🧹 [code health] enforce strict code quality and linting rules

[NITISH-R-G]

🎯 What: Enforced strict linting rules and code formatting across the repository.

💡 Why: As the autonomous GitHub Repository Controller, my directive is to continuously monitor and enforce production-grade standards. The codebase had several formatting inconsistencies, missing catch block typing, and un-bracketed single-line if statements. These have been fixed to improve maintainability and prevent errors.

✅ Verification:

• Successfully ran dart fix --apply and custom scripts to fix lints.
• Manually applied dart format . across the repository.
• Verified zero warnings and zero errors via dart analyze.
• Verified no logic regressions by successfully running the full flutter test suite.

✨ Result: The repository now conforms to stricter linting standards (avoid_print, prefer_final_fields, avoid_catches_without_on_clauses, curly_braces_in_flow_control_structures, control_flow_in_finally), ensuring a cleaner, safer, and more maintainable Dart codebase.

---

PR created automatically by Jules for task 4732901410009148907 started by @NITISH-R-G

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.