Inline true for privateTurboModulesEnabled in DefaultNewArchitectureEntryPoint.loadWithFeatureFlags (#56924)

Summary:
Pull Request resolved: #56924

The `useTurboModules` flag is being deleted; it always returns true on the canary release stage. The internal `DefaultNewArchitectureEntryPoint.loadWithFeatureFlags()` reads `featureFlags.useTurboModules()` into `privateTurboModulesEnabled` — replace the read with a literal `true`.

This matches the existing treatment of `fabricEnabled` and `concurrentReactEnabled`, which are already always `true`.

Behavior is unchanged.

Changelog:
[Internal]

Reviewed By: fkgozali

Differential Revision: D105718209

fbshipit-source-id: d03f0bb63d46b61625e7b4b74cadfa44a7787461

Author: mdvacca

packages/react-native/ReactAndroid/src/main/java/com/facebook/react/defaults/DefaultNewArchitectureEntryPoint.kt

@@ -112,7 +112,7 @@ public object DefaultNewArchitectureEntryPoint {
   internal fun loadWithFeatureFlags(featureFlags: ReactNativeFeatureFlagsProvider) {
     ReactNativeFeatureFlags.override(featureFlags)
 
-    privateTurboModulesEnabled = featureFlags.useTurboModules()
+    privateTurboModulesEnabled = true
     privateBridgelessEnabled = featureFlags.enableBridgelessArchitecture()
 
     val (isValid, errorMessage) =