add publishing credentials to repo secrets

[MoLow]

since this repo is under the node.js org - there should be a way for @nodejs/build to publish a new version.
that can be done either by adding a repository secret and a GitHub actions flow to publish a version or by adding credentials to https://github.com/nodejs-private/secrets

[MoLow]

added to the tsc-agenda so we can discuss - this and #54 seem stuck with only a single individual having credentials to release this.
@mhdawson - I am not sure if this repo is part of the automation to be added to TSC meetings, so lets make sure it is added manually if not

[mhdawson]

@MoLow the tool looks across the org so as long as it is under nodejs.org it should appear on the agenda.

[legendecas]

Using OIDC provided by GitHub Action, we don't have to save credentials or secrets to publish pypi packages, like how gyp-next is published. As a nodejs account is created in nodejs/admin#863, I believe this can move forward and untag tsc-agenda ?

[benjamingr]

@MoLow should this be discussed or is @legendecas 's suggestion sufficient?

[MoLow]

I am planning on implementing the suggestion. until I verify it - I removed the issue from the agenda