chore: add gyp-next updater

[legendecas]

Add automated updater for gyp-next.

Example: legendecas#1

• Add nodejs-github-bot token

[cclauss]

Nice!

[cclauss]

Suggested change

	subprocess.check_output(["git", "commit", "-m", "feat(gyp): update gyp to " + args.tag])
	subprocess.check_output([
	"git", "commit", "-m", "feat(gyp): update gyp to " + args.tag
	])

[lukekarrys]

This PR is a great idea and will help a lot so I'm +1 on landing it.

The only change I'm requesting is that to use a more specific GitHub token that is only used for updating gyp-next.

[lukekarrys]

Suggested change

# if: github.repository == 'nodejs/node' || github.event_name == 'workflow_dispatch'

[legendecas]

@lukekarrys the new token permissions are tracked at nodejs/admin#935. It has the same permission needed for release-please and gyp-next updater as:

permissions:
  contents: write
  pull-requests: write

The reason to use a token for release-please is that the token GitHub actions created by default will not trigger GitHub actions:

When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.
https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/triggering-a-workflow#triggering-a-workflow-from-a-workflow

So we need a token of @nodejs-github-bot, as requested at nodejs/admin#935.

[lukekarrys]

@legendecas Good call, I forgot about that restriction. I withdraw my previous suggestions and 👍

[lukekarrys]

@legendecas What do you think about the suggestions in the unresolved comment threads?

[legendecas]

yes, I will update the PR according to the suggestions above once the token is setup. Thanks for catching them!