Add dry runs to CI

[jablko]

What do you think about adding a dry run of the publisher and retag scripts to the CI? It would e.g. detect changes that require coordinated updates to the DT repo, and isn't too expensive, I think?

What I did was:

• Add a workflow for each of the scripts that has a --dry option (publish-packages, publish-registry, and retag). I combined the retag workflow with the existing one (update ts* tags for ATA).
• Call those from the CI workflow.
• To get them to work on GitHub Actions, I replaced defaultLocalOptions with defaultRemoteOptions if GITHUB_ACTIONS is true:

  DefinitelyTyped-tools/packages/publisher/src/publish-packages.ts

  Line 26 in 8665394

  const dt = await getDefinitelyTyped(defaultLocalOptions, loggerWithErrors()[0]);

• Add Fetch npm metadata concurrently #453 (comment) to speed it up, until the info cache is populated.
• Fix references to retag.js since f958fa4.
• Suppress this missing secrets error. They're not needed for a dry run:

  DefinitelyTyped-tools/packages/publisher/src/lib/secrets.ts

  Lines 29 to 34 in 8665394

  	export async function getSecret(secretId: Secret): Promise<string> {
  	const clientId = process.env.AZURE_CLIENT_ID;
  	const clientSecret = process.env.AZURE_CLIENT_SECRET;
  	const tenantId = process.env.AZURE_TENANT_ID;
  	if (!(clientId && clientSecret && tenantId)) {
  	throw new Error("Must set the AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, and AZURE_TENANT_ID environment variables.");

Here's an example of it working: https://github.com/microsoft/DefinitelyTyped-tools/actions/runs/2284182030