fix(ci): re-add Kotlin to CodeQL (#32); bump Flutter 3.44.5 + supabase_flutter 2.16.0

[GCHOfficial]

Summary

• Re-add Kotlin to CodeQL (Closes Re-add Kotlin to CodeQL once a CLI past 2.25.6 ships Kotlin 2.4.0 support #32). CodeQL CLI 2.26.0 / codeql-bundle-v2.26.0 (published 2026-07-08) ships the Kotlin 2.4.0 support merged in github/codeql#21970, so codeql-action@v4 no longer aborts with "Kotlin version 2.4.0 is too recent". Verified the merge commit is contained in the v2.26.0 tag and that init@v4 resolves to that bundle. Re-added the java-kotlin matrix entry (build-mode: manual → setup-java temurin 17 + flutter build apk --debug; checkout with lfs: true only for that entry, for the libdovi libmpv AAR) and refreshed the header comment to document the ≥ v2.26.0 bundle requirement.
• Flutter 3.44.4 → 3.44.5 across build.yml, codeql.yml, release.yml.
• supabase_flutter 2.15.4 → 2.16.0 (+ supabase 2.14.0, gotrue 2.26.0, realtime_client 2.11.0, passkeys_platform_interface 2.8.0). Remaining outdated transitives are held back by SDK/other constraints.

Test plan

• flutter analyze — clean
• flutter test — 141/141 pass
• CI: new Analyze (java-kotlin) CodeQL job builds and analyzes (only exercisable on GitHub runners)

🤖 Generated with Claude Code

https://claude.ai/code/session_01Pf76uZnruw81CCGZo1pQFo

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.