Use the same JavaScript engine in Debug and Release

[jaimecbernardo]

When porting native modules to react-native-windows, one of the issues developers face is the differences between building for Debug and Release in an application's default configuration.

The fact that different engines are used these means that there is some JavaScript code that runs on iOS and Android and even Windows on Debug but then fails on Windows on Release.

Examples of issues:

• Object.fromEntries is not supported in ChakraCore: fix(windows): remove use of Object.fromEntries react-native-device-info/react-native-device-info#1110
• react-native-windows 0.64 breaking previously working JavaScript code on Release: Some native module features stop working when building for Release on 0.64 #7537
• Using the WebDebugger doesn't allow making synchronous native function calls, which some modules use.

From a development point of view, these changes are at their worse when a developer is developing an application in Debug and then tries out some Release builds closer to shipping and is met with a blank screen, which is hard to debug to pinpoint which code might be causing it. It'd be good if these cases were easier to debug as well.

[asklar]

Eventually RN will move away from web debugging and onto direct debugging by default, which should take care of the disparity between debug/release. This likely requires Hermes to be fully supported #6137

[chrisglein]

This is now the default experience in RNW 0.74, as we default to direct debugging and web debugging is deprecated.
@TatianaKapos @jonthysell FYI