feat: add package.json version to process.version

[robertjcolley]

Summary

Expose the current react native version to the process. This came about from an issue with aws-chime-sdk-js and detect-browser which hindered web sockets in chime working correctly. I figured the simple fix would be to use process.version for react-native in detect browser, but there is nowhere where that gets set and I couldn't find out how to get the current react-native version in the runtime.

Changelog

[General] [Added] - Add polyfill for version to global.process.version

Test Plan

assert that react-native/package.json === global.process.version

[robertjcolley]

This is my first contribution here - what am I missing for the circleci checks? I'm not too familiar with flow

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
ios	-	universal	n/a	--

Base commit: 09b6903
Branch: main

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,297,184	+3,693
android	hermes	armeabi-v7a	7,627,682	+3,690
android	hermes	x86	8,767,828	+3,691
android	hermes	x86_64	8,706,767	+3,683
android	jsc	arm64-v8a	9,683,936	+2,103
android	jsc	armeabi-v7a	8,671,124	+2,093
android	jsc	x86	9,640,091	+2,095
android	jsc	x86_64	10,236,631	+2,103

Base commit: 09b6903
Branch: main

[NickGerleman]

This information is already exposed via Platform.constants.reactNativeVersion. See

react-native/Libraries/Utilities/Platform.ios.js

Line 33 in f5f6fd7

reactNativeVersion: {|

[robertjcolley]

Yes, it is already there. I think exposing it in the navigator will allow react native to have similar behavior in the global environment like the browser navigator. I had this in mind to be able to detect the current react native version without adding react-native as a dependency to the detect-browser

[github-actions]

This PR is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This PR was closed because it has been stalled for 7 days with no activity.