Avoid full copy of large folly::dynamic objects by switching to std::move semantics (#33621)
Avoid full copy of large folly::dynamic objects by switching to std::move semantics (#33621)

Summary:
Problem:
Current creation of ModuleConfig does a full copy of folly::dynamic object, which for large objects can cause 1000's of memory allocations, and thus increasing app's memory footprint and speed.

Fix:
Use std::move semantics to avoid copy of folly::dynamic, thus avoiding memory allocations.

## Changelog

[General] [Fixed] - Avoid full copy of large folly::dynamic objects by switching to std::move semantics

Pull Request resolved: https://github.com/facebook/react-native/pull/33621

Test Plan:
Compiled React Native for Windows
Consumed into Microsoft Excel App
Tested functionality through Microsoft Office Excel App
Viewed Memory Allocations in Debugger

Reviewed By: cortinico

Differential Revision: D35599759

Pulled By: RSNara

fbshipit-source-id: 095a961422cca4655590d2283f6955472f1f0410

janicduplessis/react-native,facebook/react-native,javache/react-native,janicduplessis/react-native,javache/react-native,facebook/react-native,janicduplessis/react-native,javache/react-native,javache/react-native,javache/react-native,facebook/react-native,janicduplessis/react-native,janicduplessis/react-native,janicduplessis/react-native,facebook/react-native,janicduplessis/react-native,facebook/react-native,javache/react-native,janicduplessis/react-native,facebook/react-native,facebook/react-native,javache/react-native,javache/react-native,facebook/react-native,facebook/react-native,javache/react-native