fix(aft): Stop propagating 2.x versions into 0.x Dart packages

[cadivus]

The Kinesis and Firehose components group a 2.x Flutter package with a 0.x Dart package but did not set propagate, so they defaulted to VersionPropagation.minor. When the summary package took a minor bump, the component version won the maxBy in Repo.bumpVersion, dragging the Dart packages onto the Flutter version line:

amplify_firehose_dart: 0.1.4 -> 2.14.0
amplify_kinesis_dart: 0.1.5 -> 2.13.0

Both packages have only ever published a 0.1.x line, and a publish is irreversible, so this would have permanently retired those lines.

Set propagate: none on Kinesis, Firehose and Connect — matching the existing Amplify Dart component, which pairs 2.x and 0.x packages for the same reason — and correct the two versions to the patch bumps they should have received. Connect escaped this cycle only because it took a patch bump; it would have hit the same problem on its next minor bump.

Problem was found here: #7283

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 40.98%. Comparing base (b0c2048) to head (24e2663).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7284      +/-   ##
==========================================
+ Coverage   40.97%   40.98%   +0.01%     
==========================================
  Files         121      121              
  Lines        8273     8273              
  Branches     3598     3598              
==========================================
+ Hits         3390     3391       +1     
+ Misses       4883     4882       -1     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.