feat: wallet supportedBrowsers from backoffice flags [SUP-868]

[Dominikkq]

What:

Wallet browser support now comes from backoffice flags instead of being
hardcoded in the API.

• A json flag like WALLET_LEDGER_SUPPORTED_BROWSERS sets supportedBrowsers
  on the wallet_ledger row in /features. This works for any feature and any
  model property, no hardcoded lists.
• Removed the hardcoded all-true browser list and the fake creation/update
  dates on merged rows.
• Invalid flags are skipped and logged.
• Unit tests updated.

Task:
SUP-868

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/@types/node	20.19.43	🟢 6.6	Details Check Score Reason Code-Review 🟢 9 Found 28/29 approved changesets -- score normalized to 9 Maintained 🟢 10 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Security-Policy 🟢 10 security policy file detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md Signed-Releases ⚠️ -1 no releases found License 🟢 9 license file detected SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Binary-Artifacts 🟢 10 no binaries found in the repo Pinned-Dependencies 🟢 8 dependency not pinned by hash detected -- score normalized to 8 Fuzzing ⚠️ 0 project is not fuzzed

Scanned Files

• package-lock.json