[ci] fix no-response permissions

[jameslamb]

Contributes to #6313

How to test this

I think we'll have to merge this PR to test, since workflow_dispatch (the thing that lets you click a button and run it from an arbitrary branch) isn't set up for this workflow.

In this PR, I'm also proposing adding a workflow_dispatch trigger, so we can do that type of testing in the future if needed.

Notes for Reviewers

Looks like the lock-bot config already uses this:

LightGBM/.github/workflows/lock.yml

Lines 10 to 12 in 6330d62

	permissions:
	issues: write
	pull-requests: write

And it shouldn't affect triggering-comments stuff like the valgrind checks, as those use a different secret:

LightGBM/.github/workflows/triggering_comments.yml

Lines 11 to 12 in 6330d62

	env:
	SECRETS_WORKFLOW: ${{ secrets.WORKFLOW }}

[jameslamb]

@shiyu1994 can you please restart the VM running for the CUDA jobs? Seems those jobs are getting stuck waiting for a runner to pick them up.

[jameslamb]

thanks for the help @shiyu1994

[github-actions]

This pull request has been automatically locked since there has not been any recent activity since it was closed.
To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.