Previously, we manually copied the `tarball/content` folder over when bootstrapping the VMR. Now it is handled by the darc tooling when you point it to the right dir.
Adds a pipeline that will trigger on main commits and synchronize the [VMR](https://github.com/dotnet/dotnet).
The pipeline has 2 parameters:
- What commit of installer to sync to (defaults to commit that triggered the build)
- What branch of the VMR it pushes to (defaults to branch that triggered the build)
Previously, the recursive clone of all the product repos based on `Version.Details.xml` files was done inside MSBuild but the VMR tooling can now do that (https://github.com/dotnet/arcade-services/pull/2004).
This replaces the need for the Source-Build tasks (Read/Write, recursive clone).
Secondly, `git-info` props files are now created by the CLI too (https://github.com/dotnet/arcade-services/pull/2014).
Adds the possibility to initialize a fresh VMR off of the current `dotnet/installer` commit.
Similarly to the tarball generation, the process can be triggered by running:
```
./build.sh /p:InitializeVMR=true /p:VmrDir=[Path were VMR will be created]
```
