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.

使用提供的 GitHub Actions 工作流和 comment 命令重现该失败，然后检查操作日志中出现的 src/functions/prechecks.js 和 src/main.js。检查 prechecks 请求如何处理报告的权限错误，以及调试输出在哪里发出。完成的标准是能够识别缺少的权限，并且该操作提供有用的调试详细信息。

由索引模型根据 Issue 内容生成。