Update to the latest pigeon

[natebosch]

The current version is incompatible with the latest analyzer, which is a blocker for getting the latest mockito, which is a blocker for getting the latest test_api, which is pinned by flutter_test and will be breaking in the next package roll.

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

[stuartmorgan-g]

This is missing the updates required to release it: https://github.com/flutter/flutter/wiki/Contributing-to-Plugins-and-Packages#version-and-changelog-updates

[stuartmorgan-g]

Never mind, I forgot this is still publish_to: none

[gmackall]

LGTM

I've also actually tried running the sample app with the generated code from this version of pigeon already (because I was curious about the generated FlutterError exception in 9.1.0), and I didn't run into any issues.

[stuartmorgan-g]

because I was curious about the generated FlutterError exception in 9.1.0

It doesn't do anything unless you use it. You can throw it instead of a generic RuntimeException in order to better control how the Dart-side PlatformException is populated from it, since the default RuntimeException->PlatformException translation isn't all that helpful in making good errors.

[Hixie]

test-exempt: dependency roll

[gmackall]

because I was curious about the generated FlutterError exception in 9.1.0

It doesn't do anything unless you use it. You can throw it instead of a generic RuntimeException in order to better control how the Dart-side PlatformException is populated from it, since the default RuntimeException->PlatformException translation isn't all that helpful in making good errors.

Yes, I didn't realize that the Runtime->Platform was the default approach and it felt weird enough to me that I was looking around at what else was possible, but I ended up just sticking with it.

[stuartmorgan-g]

If you're returning any errors in camerax, I definitely recommend updating to using FlutterError everywhere when you have a chance :)