deps: Bump flutter_secure_storage from 10.3.1 to 10.3.4

[dependabot]

Bumps flutter_secure_storage from 10.3.1 to 10.3.4.

Release notes

Sourced from flutter_secure_storage's releases.

flutter_secure_storage: v10.3.2

Backport release for the v10 line. 11.0.0 remains the current major version.

10.3.2 (2026-09-09)

Android

• Fixed data loss when switching between sharedPreferencesName and storageNamespace with the same name; the wrapped key is now moved to the new location instead of the store starting empty.
• Fixed v9 data with a non-default keyCipherAlgorithm/storageCipherAlgorithm being discarded on upgrade: its algorithm markers were stored where v10 doesn't look, so a failed migration deleted it. Markers are now read from the v9 location, and unmarked data that still decrypts with the current cipher is left alone.
• Fixed AES-GCM data from v9 becoming unreadable: v9's wrapped-key preference name had a typo that v10 corrected, and is now read as a fallback.
• Fixed migrateWithBackup ignoring storageNamespace and backing up the wrong key storage file.
• Fixed a migration running on a fresh install, which could fail on some devices' KeyStore.
• Fixed a NullPointerException when a storage call ran after the Flutter engine detached; it now throws a catchable INIT_FAILED PlatformException.

Commits

• 692a374 Merge pull request #1261 from juliansteenbakker/fix/biometric-multi-instance-...
• 16b0924 docs: trim and tighten comments added on this branch
• f122654 doc: update doc
• 23a5d7d Merge branch '10.x' into fix/biometric-multi-instance-race
• b96721b doc: update doc
• 0ca5c3c Merge pull request #1260 from juliansteenbakker/fix/legacy-namespace-key-reco...
• 20b7011 chore: consolidate into a single v10.3.4 release
• 7279651 release of v10.3.6
• cc8c73b release of v10.3.4
• 0aadfa9 fix(android): don't touch a sibling instance's Keystore key on a fresh install
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.