Fixed wrong usage of require when resolving supportsCodegenConfig in …

…react-native.config.js (#657)

* Fixed wrong usage of require when resolving supportsCodegenConfig

When resolving the version inside `react-native-config` which is used by the autolinking gradle tasks, the wrong use of require was used.

This fix changes from using `require.main.require` -> `require`.

The difference is that require.main.require resolves from the entry point (main script), while require resolves from the location of the current file.

* Codereview: Removed test for code gen alltogether

package/react-native.config.js

@@ -1,24 +1,11 @@
-let supportsCodegenConfig = false;
-try {
-  const rnCliAndroidVersion = require.main.require(
-    '@react-native-community/cli-platform-android/package.json',
-  ).version;
-  const [major] = rnCliAndroidVersion.split('.');
-  supportsCodegenConfig = major >= 9;
-} catch (e) {
-  // ignore
-}
-
 module.exports = {
   dependency: {
     platforms: {
-      android: supportsCodegenConfig
-        ? {
-            libraryName: 'RNCSlider',
-            componentDescriptors: ["RNCSliderComponentDescriptor"],
-            cmakeListsPath: 'src/main/jni/CMakeLists.txt',
-          }
-        : {},
+      android: {
+        libraryName: 'RNCSlider',
+        componentDescriptors: ['RNCSliderComponentDescriptor'],
+        cmakeListsPath: 'src/main/jni/CMakeLists.txt',
+      },
     },
   },
 };