Add NPM publishing

[mikesellitto]

This PR updates the existing publish GitHub Action to publish the package to NPM when a version tag is pushed.

Closes ENG-9060

[linear]

ENG-9060 Add GH actions workflow to build+publish package

This workflow will be triggered on the "push tags" event similar to the TF provider, which will enable us to cut versions using the "releases" interface within GitHub. This process should:

• Replace the version in ~~package.json~~ with the version in the tag, and set ~~private: false~~.
• Fetch the latest OpenAPI spec to include in the published package.
• Transpile all typescript.
• Run a minimal test to ensure that the application can actually start up using this OpenAPI spec.
• Publish the package to NPM.
  • The credential will be stored in GitHub Actions and available to the workflow, the name of that secret is TBD.

[mikesellitto]

@emily-curry The ticket mentions something like "the credential secret will be available to the workflow" so I take we're using an access token as opposed to OIDC. If we are instead using OIDC I'll add this back and remove the NODE_AUTH_TOKEN: ${{ secrets.NPM_ACCESS_TOKEN }} below

[emily-curry]

We are using OIDC, npm doesn't allow for long-lived access tokens so we don't want to be generating them all the time. I've already set up the trust relationship between this repo and our account.

[mikesellitto]

reverted in the latest force push

[mikesellitto]

note to reviewers: We don't need this prepublish build anymore since the action runs npm run build before the smoke test (node dist/index.js --help)