Fix NPM dist tags and make some NPM private

[vmoroz]

Description

Make sure that the NPM packages that are meant to be private are private.
Use the same release NPM tag (dist-tag) for all packages released from from the same branch.

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Why

In the previous attempt to fix the publish/release pipeline I implemented sorting of all NPM packages by the dirst-tag that they use: latest vs custom. The custom dist-tag being tags like "canary", "preview", etc.
The sorting not always work correctly and using the "latest" tag creates issues in non-main release branches.
After discussing this issue with @tido64 and @acoates-ms , we realized that the root cause is that we have several packages that are missing "private": true in their package.json since they are meant to private. Also, all packages published from the same branch must have the same dist-tag.

What

This PR has the following changes:

• Adds the missing "private": true to package.json files that are meant to be private.
• Ensures that all public packages have the "canary" dist-tag.
• Removes now unnecessary npmGroupByTag.js script
• Removes publishing NPM packages from publish.yml. They are published from release.yml as Nuget packages only after the whole Publish pipeline succeeds.
• setVersionEnvVars.js is changed to provide the npmDistTag based on the react-native-windows package defined in the vnext\package.json.
• The release.yml stages are changed to jobs. This way we can run publishing in parallel and be able to recover pushing to specific component registry independently from each other.

Testing

No testing is done yet. We will have to fix the pipeline later if we see the issues.
We do not expect issues with the publish.yml since we only removed steps there.
If any issues happened in release.yml, then we can recover manually and fix the script after that,

Changelog

Should this change be included in the release notes: no

Microsoft Reviewers: Open in CodeFlow