Bugzilla

After [investigating Bug 1837446](https://bugzilla.mozilla.org/show_bug.cgi?id=1837446#c3) and looking at Bug 1837498, there is a hypothesis that the config change flags in the manifest are causing some complex bugs. The config change flags may be causing the Composables to not properly recompose because those configuration change events are being ignored or manually handled.

As part of the work for this ticket, investigate removing these flags (at least from [`HomeActivity`](https://searchfox.org/mozilla-mobile/source/firefox-android/fenix/app/src/main/AndroidManifest.xml#104)) and the work that would result from this, as there are a few areas of the app that override `onConfigurationChanged` such as `TabsTrayFragment`, `FenixApplication`, and `OnboardingFragment`. 

After briefly discussing this with Jeff, it sounds like there was a historical reason for adding these flags that is no longer needed today.

After [investigating Bug 1837446](https://bugzilla.mozilla.org/show_bug.cgi?id=1837446#c3) and looking at Bug 1837498, there is a hypothesis that the config change flags in the manifest are causing some complex bugs. The config change flags may be causing the Composables to not properly recompose because those configuration change events are being ignored or manually handled.

As part of the work for this ticket, investigate removing these flags (at least from [`HomeActivity`](https://searchfox.org/mozilla-mobile/source/firefox-android/fenix/app/src/main/AndroidManifest.xml#104)) and the work that would result from this, as there are a few areas of the app that override `onConfigurationChanged` such as `TabsTrayFragment`, `FenixApplication`, and `OnboardingFragment`. 

After briefly discussing this with Jeff, it sounds like there was a historical reason for adding these flags that is no longer needed today.

For v1, remove the flags from the Debug manifest and let it bake for a period of time before removing them from the main manifest.