ci: update lock file through nx.json flag instead (#2476)

## Summary:

This reverts commit 791012b.

We had some custom logic to update the lock file after the "version"
step of release happened. Turns out you can just do that directly
through `nx`... so let's remove the logic and do it that was instead.

## Test Plan:

Ran `nx release --skip-publish` locally (and cmd+c'ed it before it
committed anything...) to see if the lock would update with the new
versions and it did.

Author: Saadnajmi

nx.json

@@ -29,8 +29,7 @@
         "currentVersionResolverMetadata": {
           "tag": "nightly"
         },
-        "preid": "nightly",
-        "skipLockFileUpdate": true
+        "preid": "nightly"
       }
     }
   }

packages/nx-release-version/index.js

@@ -3,7 +3,6 @@
 const { releaseVersionGenerator } = require('@nx/js/src/generators/release-version/release-version');
 const fs = require('node:fs');
 const path = require('node:path');
-const { spawnSync } = require('node:child_process');
 const { REPO_ROOT } = require('../../scripts/consts');
 
 /**
@@ -18,8 +17,6 @@ async function runSetVersion() {
 
   await updateReactNativeArtifacts(version);
 
-  spawnSync('yarn', ['install', '--mode', 'update-lockfile']);
-
   return [
     path.join(
       REPO_ROOT,
@@ -66,10 +63,6 @@ async function runSetVersion() {
       'Core',
       'ReactNativeVersion.js',
     ),
-    path.join(
-      REPO_ROOT,
-      'yarn.lock',
-    ),
   ];
 }