chore: add post-version step to Nx Release

[tido64]

Summary:

Adds a post-version step to Nx Release for updating generated artifacts (e.g., RCTVersion.m).

Test Plan:

Bump the version and run nx release:

yarn nx release plan --only-touched=false patch
yarn nx release --skip-publish --verbose

Verify that generated artifacts have been updated with the latest version number.

[Saadnajmi]

EDIT: This is because dry-run doesn't commit the files, so the generator fails. I'll move forward with this knowing that caveat.

---

I did a quick test by cherry-picking this to a local branch off 0.77-stable, and added these logging statements:

  const manifest = fs.readFileSync(rnmPkgJson, { encoding: 'utf-8' });
  const { version } = JSON.parse(manifest);

  console.log('SAAD');
  console.log(version);

Which resulted in this output:

...
UPDATE packages/react-native-test-library/package.json [dry-run]

  "name": "@react-native/oss-library-example",
-   "version": "0.77.2",
+   "version": "0.77.4",
  "private": true,

    "@react-native/babel-preset": "0.77.0",
-     "react-native-macos": "0.77.0"
+     "react-native-macos": "0.77.1"
  },

SAAD
0.77.0

It seems to be picking up the old version because the new version hasn't been committed yet?

Alternatively, we could use nx's releaseVersion function (which is part of their public API) to get the new version as I do in #2417:

    const { workspaceVersion, projectsVersionData } = await releaseVersion({
       specifier: options.version,
       dryRun: options["dry-run"],
       verbose: options.verbose,
   });
   const newRNMVersion = projectsVersionData["react-native-macos"].newVersion;