Fix Flutter upgrade to v3.19

[evdokimovs]

Synopsis

The Flutter team has recently released Flutter v3.19, leading to conflicts with certain dependencies of medea-jason on the latest Flutter release. Consequently, the CI is currently broken. This PR resolves these issues.

Solution

Upgrade ffigen dependency version to 11.0.0.

Checklist

• Created PR:
  • [x] In draft mode
  • [x] Name contains issue reference
  • [x] Has type and k:: labels applied
  • [x] Has assignee
• Before review:
  • [x] Documentation is updated (if required)
  • [x] Tests are updated (if required)
  • [x] Changes conform code style
  • [x] CHANGELOG entry is added (if required)
  • [x] FCM (final commit message) is posted or updated
  • [x] Draft mode is removed
• [x] Review is completed and changes are approved
  • [x] FCM (final commit message) is approved
• Before merge:
  • [x] Milestone is set
  • [x] PR's name and description are correct and up-to-date
  • [x] All temporary labels are removed

[tyranron]

@evdokimovs please, do the same also in medea-flutter-webrtc.

[evdokimovs]

FCM

Fix Flutter upgrade to 3.19 version (#152)

- upgrade `ffigen` Dart package to 11.0.0 version

[evdokimovs]

@tyranron ,

@evdokimovs please, do the same also in medea-flutter-webrtc.

As I see, update to Flutter v3.19 doesn't breaks anything in medea-flutter-webrtc, because it doesn't use flutter_gherkin. It's still better to upgrade ffigen to the newest version even if it's not required, but in case of medea-flutter-webrtc it's better to wait till flutter-rust-bridge will bump version of ffigen on their side before doing it, because otherwise it will break code generation in medea-flutter-webrtc.

I will create PR for this in FRB, so it shouldn't take long.

Also I thinking about adding codegen check job to CI, because sometimes some PR modifies some code related to codegen, but forgets to regenerate Dart code (documentation for example).