Update Release process doc (#5159)

Author: anrossi

docs/Release.md

@@ -141,6 +141,8 @@ The following are the complete (manual) steps for publishing the Rust crate.
 
 ## Synchronizing with Windows
 
-1. Once the release branch is created, set the pipeline [here](https://mscodehub.visualstudio.com/msquic/_build?definitionId=1868) to ingest the release branch into Windows, and run it.
-2. When the pipeline passes tests, it'll create a PR.
+1. Once the release branch/tag is created, the undock pipeline should run automatically.
+   - If for some reason there's a problem, you may need to run the pipline manually by clicking on "Run Pipeline" [here](https://microsoft.visualstudio.com/undock/_build?definitionId=134439) (MSFT-only access required), scroll down to the **resources tab** and pick the MsQuic release tag of interest then run the pipeline.
+   - Another workaround to force a manual re-run by going [here](https://microsoft.visualstudio.com/undock/_git/msquic/tags) (MSFT-only access required) and deleting the tag, and then waiting for the [mirror pipeline](https://microsoft.visualstudio.com/undock/_build?definitionId=134727) (MSFT-only access required) to run automatically re-copy over the tag from GitHub.
+2. Once the pipeline passes tests, get the VPACK ID from the "Create VPACK" stage, and create a PR to point [this file](https://microsoft.visualstudio.com/OS/_git/os.2020?path=/minio/netio/quic/msquic/msquic.man) (MSFT-only access required) to the VPACK created by the pipline run.
 3. Review and merge the PR to complete the process.