fix(mix_generator): support analyzer 14

[definev]

Related issue

No linked issue.

Description

Allow mix_generator to resolve with analyzer 11–14, including 14.4.0. Modifier generation now uses field-origin metadata after analyzer removed FieldElement.isSynthetic, while continuing to exclude static fields and fields induced by getters/setters.

Changes

• Support analyzer >=10.0.0 <15.0.0 in mix_generator; the replacement field-origin API sets the new minimum to analyzer 10.
• Add a regression that resolves generated modifier code containing static fields, a computed getter, and a setter.
• Update root and protocol tooling to analyzer >=13.0.0 <15.0.0, migrating named arguments and formal parameters to the current AST APIs.
• Update the generator changelog and repository dependency notes.

Review Checklist

• Testing: 380 generator tests pass with analyzer 10.0.0 and 14.4.0; 22 protocol inventory tests pass. Actual Mix generation passes with analyzer 13 without changing generated output.
• Breaking Changes: Minimum supported analyzer increases from 9 to 10; emitted runtime APIs are unchanged.
• Documentation Updates: Changelog and repository dependency notes updated.
• Website Updates: No website documentation changes required.

Additional Information

Generator analysis has no errors or warnings, with four existing prefer_initializing_formals infos. Root scripts and protocol inventory tooling analyze cleanly. melos run gen:build and melos run ci pass across the repository; regenerated files are unchanged. Schema inventories and melos run analyze:dart pass. melos run analyze reaches DCM, then fails because dcm is not installed locally.

[definev]

@leoafarias please take a look at my PR. It's blocking us from using mix in production because we rely on other generators that use a newer analyzer version.

[leoafarias]

Released in mix_generator 2.2.1. Thanks for the contribution!

[definev]

Thank you 💙