"NPM Publish Dry Run" CI job fails if a version plan is present

[Saadnajmi]

This can be fixed in two ways:

1. Moving the job to Github Actions, and using the built in GITHUB_TOKEN (long task)

• For this to be viable, we have to move the whole release flow to Github Actions, but keep "NPM Publish" on Azure Pipelines for compliance reasons

2. Setting up a minimal CI task to generate a short lived readonly Github PAT, similar to nx release will always publish NPM packages with tag latest nrwl/nx#30979

• Need to do this anyway for compliance reasons. RNW wants to do the same.

So the choice basically becomes: When we move to make our CI more compliant, do we convert most of it to Github Actions so we can use the built in Github Token, or do we maintain a minimal fork of https://github.com/actions/create-github-app-token that we can run on Azure pipelines?