chore(flutter): upgrade to 3.41.0 + iOS UIScene migration

[CowboyGH]

🚀 Summary

Flutter 3.41.0 upgrade + iOS UIScene migration.

✨ Changes

• ✅ Upgraded Flutter SDK from 3.38.4 to 3.41.0 in CI/CD workflows and Docker container builds
• ✅ Auto-migrated UISceneDelegate (iOS 17+)
• ✅ Firebase + deps refreshed (CocoaPods)
• ✅ Added iOS build artifacts directory to project ignore patterns

🧪 Verification

• flutter run/build ios
• flutter analyze
• flutter test
• CI checks pass

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• ✅ Review completed - (🔄 Check again to review again)

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/flutter-3.41-upgrade

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@ios/Runner/Info.plist`:
- Around line 25-35: The project is missing the GoogleService-Info.plist
referenced by the iOS build and Firebase init; download the correct
GoogleService-Info.plist from your Firebase Console for this app, add it to the
Xcode project, make sure it is included in the app target and in Copy Bundle
Resources, and then verify the existing Info.plist entries (CFBundleURLSchemes
and GIDClientID) match the values in the GoogleService-Info.plist.

🧹 Nitpick comments (1)

Dockerfile (1)

5-5: Add checksum validation for Flutter 3.41.0 download to mitigate supply-chain risk.

Flutter 3.41.0 stable (released Feb 10, 2026) includes official SHA256 checksums published in the releases_linux.json manifest. Consider adding checksum validation to verify the tarball integrity:

🔐 Checksum validation (recommended)

 ARG TARGETPLATFORM=linux/amd64
 ARG FLUTTER_VERSION=3.41.0
+ARG FLUTTER_SHA256=<sha256_from_releases_linux.json>
 
-RUN wget -q https://storage.googleapis.com/flutter_infra_release/releases/stable/linux/flutter_linux_${FLUTTER_VERSION}-stable.tar.xz -O /tmp/flutter.tar.xz && \
+RUN wget -q https://storage.googleapis.com/flutter_infra_release/releases/stable/linux/flutter_linux_${FLUTTER_VERSION}-stable.tar.xz -O /tmp/flutter.tar.xz && \
+    echo "${FLUTTER_SHA256}  /tmp/flutter.tar.xz" | sha256sum -c - && \
     tar xf /tmp/flutter.tar.xz -C /opt && \
     rm /tmp/flutter.tar.xz

Retrieve the checksum via:

curl -s https://storage.googleapis.com/flutter_infra_release/releases/releases_linux.json | jq -r '.releases[] | select(.channel=="stable" and .version=="3.41.0" and .archive=="stable/linux/flutter_linux_3.41.0-stable.tar.xz") | .sha256'