Description

We currently have a way to define the version of Flutter that we use. With that comes an implicit tie to certain versions of frameworks/packages including Dart and the intl package (assuming there are others as well). By either looking at the Flutter install or just creating a new Flutter project we should be able to understand which framework/package versions we need to be pinned to and using so we don't have dependency upgrade errors.

Requirements

• All CI/CD checks are passing.
• There is no drop in the test coverage percentage.
• We have a way to determine the needed pinned frameworks/packages (at a minimum Dart and intl)
• The dependency tighter tool no long attempts to update pinned packages

Additional Context

This was originally discovered when he dependency tightener action updated the intl package as it was updated to 0.20.0 but the version of Flutter we are using 3.24.0 is pinned to the previous version 0.19.0