fix(ci): use PAT when filing scenario reports so project workflows run

[BigLep]

Problem

Nightly scenario reporting (via ci_nightly.yml → reusable ci_run.yml) creates or updates GitHub issues for runs like the frontier/stability reports (similar in spirit to foc-devnet#96).

The Add issues and PRs to FS project board workflow (and other issues: opened automation) was not running for those issues.

Per GitHub Actions behavior, events triggered with the default GITHUB_TOKEN / github.token do not start other workflows (except cases such as workflow_dispatch / repository_dispatch). So ipdxco/create-or-update-issue using github.token produced issue activity that did not cascade to org/repo workflows that listen for new issues.

Specifically I want it so future issues like #95 and #96 show up on our project board.

Change

• Use secrets.FILOZZY_RELEASE_PLEASE_PAT_FILOZONE as the token passed to create-or-update-issue so issue open/update behaves like normal bot/user API activity and downstream workflows can run.
• ci_nightly.yml and ci_pull_request.yml already call the reusable workflow with secrets: inherit; no caller changes.

Notes from code review (inline comments in ci_run.yml)

• We avoid github.token here because it does not trigger other workflows such as add-issues-to-project-style automation.
• A PAT is used so those workflows do run.
• The chosen PAT already has permission to open/update issues; a narrower-scoped PAT would be possible but adds another secret to set up and manage.

Checklist

• Confirm FILOZZY_RELEASE_PLEASE_PAT_FILOZONE is configured for FilOzone/foc-localnet (or inherited from org) with sufficient scopes to create/update issues and labels in this repo.

Made with Cursor

[BigLep]

FilOz bot has access to the repo: https://github.com/FilOzone/foc-devnet/settings/access

PAT has appropriate access: https://github.com/organizations/FilOzone/settings/personal-access-tokens/1277607

[Copilot]

Pull request overview

Updates the reusable CI workflow to file/update scenario report issues using a Personal Access Token (PAT) instead of the default github.token, so that downstream automation workflows triggered by issues events (e.g., adding issues to a project board) will run as expected.

Changes:

• Swap github.token for secrets.FILOZZY_RELEASE_PLEASE_PAT_FILOZONE when calling ipdxco/create-or-update-issue@v1.
• Add inline documentation explaining why a PAT is required for cascading issues-triggered workflows.