feat: allow rebuilding parser artifacts

[DerekStride]

What

The DerekStride/tree-sitter-sql project doesn't have the parser artifacts published to the main branch and needs the python workflow to allow optionally regenerating them.

This PR adds a new input that will run tree-sitter generate when set to true.

Questions

• What's a good input parameter name? I started with rebuild-parser
• How should the regeneration be done? I reused the steps from the regenerate.yml workflow but that required setting up Node.
  • The setup-action might be a better option

workflows/.github/workflows/regenerate.yml

Lines 49 to 57 in 614fc22

	- name: Set up NodeJS
	uses: actions/setup-node@v4
	with:
	cache: npm
	node-version: ${{inputs.node-version}}
	- name: Regenerate parser
	run: |-
	npm ci --legacy-peer-deps
	npm x -- tree-sitter generate --no-bindings

[ObserverOfTime]

• This should be added to all packaging workflows.
• It should indeed use the setup-action.
• The name should be "generate".

[DerekStride]

Made the suggested changes and tested the workflow on the tree-sitter-sql project:

• Test Branch
• Test Workflow (same as this PR w/ removed secret via ef7f2f1 to prevent publishing)
• Action Run fails because of the removed secret to prevent accidentally publishing