Getting started not working

### Describe the Issue

I'm trying this action in an empty repository and I'm not able to make it working. It says something about missing permissions but it's not specifying which one is missing.

I put the attached workflow in main branch, then I opened a pull request and commented it with

```
.ping | LOG_LEVEL=debug,CPU_CORES=4
```

### Action Configuration

```yaml
name: "command demo"

# the workflow to execute on is comments that are newly created
on:
issue_comment:
types: [ created ]

# permissions needed for reacting to IssueOps commands on issues and PRs
permissions:
pull-requests: write
issues: write
checks: read

jobs:
demo:
runs-on: ubuntu-latest
steps:
# execute IssueOps command logic, hooray!
# this will be used to "gate" all future steps below
- uses: github/command@v1.2.2
id: ping
with:
command: ".ping"

# run your custom logic for your project here - example seen below

# conditionally run some logic here
- name: ping command
if: ${{ steps.ping.outputs.continue == 'true' }}
run: echo 'Got comment in PR \#${{ steps.ping.outputs.issue_number }} with params ${{ steps.ping.outputs.params }}'
```

### Relevant Actions Log Output

```
Run github/command@v1.2.2
##[debug]checking if the context of 'issue_comment' is valid
🧮 detected parameters in command: LOG_LEVEL=debug,CPU_CORES=4
##[debug]raw allowlist value: false
##[debug]no allowlist provided, all users are allowed
Error: GraphqlResponseError: Request failed due to following response errors:
- Resource not accessible by integration
at /home/runner/work/_actions/github/command/v1.2.2/node_modules/@octokit/graphql/dist-node/index.js:113:1
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at prechecks (/home/runner/work/_actions/github/command/v1.2.2/src/functions/prechecks.js:129:1)
at run (/home/runner/work/_actions/github/command/v1.2.2/src/main.js:78:1)
Error: Request failed due to following response errors:
- Resource not accessible by integration
```

### Extra Information

It would be very useful if the action uses some `core.debug` calls in its codebase to better track issues like this one. At the moment even with debug mode there is no output from the action itself.

Reproduce the failure with the supplied GitHub Actions workflow and comment command, then inspect src/functions/prechecks.js and src/main.js, which appear in the action log. Check how the prechecks request handles the reported permission error and where debug output is emitted. Done means the missing permission is identifiable and the action provides useful debug details.

Written by the indexing model from the issue text.