Localization: extract SwiftUI `Text("…")` strings (after a `Text(verbatim:)` cleanup pass)

The build-free String Catalog generation lane (generate_strings_catalog, added in #25688) can extract SwiftUI Text("literal") strings via xcstringstool extract --SwiftUI-Text, but it's gated behind a swiftui: parameter and off by default. This issue tracks turning it on.

Why it's off today

The app currently has ~94 Text("…") literals but only 16 Text(verbatim:). With --SwiftUI-Text on, xcstringstool would extract every Text("…") literal — including non-translatable ones like single glyphs/characters (Text("Aa"), Text("A")) — and feed them to translators as garbage. So it's a deliberate coverage expansion that needs a cleanup pass first.

What's needed

1. Audit the Text("…") literals and convert the non-translatable ones (glyphs, single characters, symbols, non-words) to Text(verbatim:), so they're correctly excluded from extraction.
2. Enable extraction — pass swiftui: true to generate_strings_catalog (flips --SwiftUI-Text on in extract_stringsdata).

References

• Code: fastlane/lanes/localization_catalog.rb — the swiftui: flag and the extract_stringsdata comment.
• PR: #25688

Until this lands, SwiftUI Text("…") strings are not extracted or localized by the catalog pipeline (the legacy genstrings / AppLocalizedString paths are unaffected).

Start in fastlane/lanes/localization_catalog.rb to inspect the swiftui flag and the extract_stringsdata comment, then audit the app's SwiftUI Text("…") literals for glyphs, single characters, symbols, and other non-words. Convert those cases to Text(verbatim:), enable swiftui: true, and verify that the catalog pipeline extracts translatable strings without the excluded literals.