Fix debugOptimized DevSettingsActivity manifest

[Phecda]

Summary:

Fixes #57396.

debugOptimized builds still expose the React Native Dev Menu Settings item, but DevSettingsActivity was only declared in the debug manifest. This caused Settings to crash in debugOptimized with ActivityNotFoundException.

This adds a debugOptimized manifest matching the existing debug dev-support manifest, so DevSettingsActivity is declared for that build type.

Changelog:

[ANDROID] [FIXED] - Fix Dev Menu Settings crash in debugOptimized builds

Test Plan:

Verified with RNTester debugOptimized:

yarn install --frozen-lockfile
yarn start
./gradlew :packages:rn-tester:android:app:installDebugOptimized -PreactNativeArchitectures=arm64-v8a

then shake and tap Settings, confirm that Debug Settings opens instead of crashing.

[Phecda]

Additional context: this crash is more noticeable in debugOptimized because Settings is currently the only Dev Menu path that persists the Metro host through debug_http_host.

Change Bundle Location updates the current PackagerConnectionSettings.debugServerHost, but that setter only updates the in-process cached host. It does not write the new value to SharedPreferences, so the change is lost after killing and restarting the app.

This PR only fixes the Settings crash by making DevSettingsActivity available for debugOptimized.

[cortinico]

Can you add a comment explaining why this manifest is needed and that it hsould be kept in sync with the devsupport one?

[Phecda]

Hi, I added a comment. I kept this manifest aligned with the debug DevSupport manifest because debugOptimized still enables DevSupport/Dev Menu while using optimized native code, so debug-only DevSupport entries such as DevSettingsActivity and the legacy FPS overlay permission should remain available.

[meta-codesync]

@cortinico has imported this pull request. If you are a Meta employee, you can view this in D110463462.

[meta-codesync]

@cortinico merged this pull request in 2fb4f13.