ci(github): use app token for dependabot merges

[ncipollina]

Summary

Updates the Dependabot auto-merge workflow to use the LayeredCraft GitHub App token for approving and enabling auto-merge. This avoids using GITHUB_TOKEN for the merge operation so downstream workflows can run after Dependabot auto-merged changes land on main.

Changes

• Adds a SHA-pinned actions/create-github-app-token step for semver patch/minor Dependabot PRs.
• Uses the generated app token as GH_TOKEN for gh pr review --approve and gh pr merge --auto --squash.
• Keeps dependabot/fetch-metadata on the default GITHUB_TOKEN.

Validation

• Reviewed workflow syntax and token usage.
• No build required; workflow-only change.

Notes for Reviewers

Requires the Actions secrets DEPENDABOT_AUTOMERGE_APP_ID and DEPENDABOT_AUTOMERGE_PRIVATE_KEY to be available to this repository.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f0bffadb50

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use a secret-accessible trigger for the app token

For the Dependabot-authored pull_request_target runs selected by this job, GitHub's Dependabot-on-Actions restrictions say secrets are not available, so these new app-id/private-key inputs resolve empty and actions/create-github-app-token fails before the approval or auto-merge steps run. Move the app-token work to a trigger that can access Actions secrets, such as a follow-up workflow_run, or use another authentication path that does not require unavailable secrets.

Useful? React with 👍 / 👎.