Commit changes when failing VS AutoLinkCheck

In VS Builds we run nx react-native autolink-windows --check, which does a dry run of autolinking logic. This is done to avoid mutating build files during the actual build.

An alternate approach is to write the files, then fail the build, messaging the user that their files were updated. This still requires multiple builds, but removes a trip to the command-line for manual steps.

As a proof of concept I tried the following sequence of events:

1. Started a build
2. Mutated packages.config during the build
3. Canceled the build
4. Started a solution build

The new NuGet package was restored on the next build, meaning we should be able to fail the build a single time and have changes picked up the next.

So, we could change the current:

Warning: Auto-linking changes were necessary but '--check' was specified. Run 'npx react-native autolink-windows' to apply the changes.

to

Auto-linking updated your project. Please rebuild for changes to take effect.

Start by tracing the VS Builds invocation of nx react-native autolink-windows --check and the handling of its warning. Review how packages.config is mutated and restored during the next solution build. Done means the build updates the project, reports that a rebuild is required, and no longer instructs users to run the command manually.