Bump win32 to ^6.0.0 in flutter_secure_storage_windows

[PAzter1101]

Problem

flutter_secure_storage_windows 4.1.0 (latest) pins win32: ^5.5.4, blocking downstream packages that have already migrated to win32 ^6.0.0:

• wakelock_plus ≥ 1.6.0
• device_info_plus ≥ 13.0.0
• share_plus ≥ 13.0.0

Any Flutter project depending on both flutter_secure_storage ^10.x and any of the above hits unresolvable version conflict:

Because flutter_secure_storage_windows 4.1.0 depends on win32 ^5.5.4 and …
version solving failed.

Impact

Mobile-only projects (Android/iOS) pay the cost of a Windows-only transitive dep blocking the resolve. Workaround for now is dependency_overrides: win32: ^6.0.0 in the consumer pubspec, which is safe because flutter_secure_storage_windows isn't built for Android/iOS targets — but it's a papercut for many downstream users and isn't discoverable.

Suggested fix

Bump win32 dependency in flutter_secure_storage_windows/pubspec.yaml to ^6.0.0.

Note that win32 6.0.0 is a breaking release (BOOL→bool, HRESULT→WindowsException throws, enum constants→extension types). The Credential Manager calls in flutter_secure_storage_windows_ffi.dart (CredWriteW, CredReadW, CredDeleteW, CREDENTIALW, CRED_TYPE_GENERIC) will need signature updates and Windows-build verification.

Happy to contribute a PR if there's interest — opening an issue first to check the preferred path and coordinate with other work on the package.

Environment

• flutter_secure_storage: 10.0.0
• flutter_secure_storage_windows: 4.1.0
• Flutter: 3.41.5
• Target platforms: Android, iOS

[PAzter1101]

Just noticed PR #1096 is already open and addresses exactly this — closing as duplicate. 👍

Looks like the PR is waiting on final review after the @juliansteenbakker's CHANGES_REQUESTED feedback was addressed (bumping to flutter_secure_storage_windows 4.2.0 to reflect the breaking win32 upgrade).