Use push_token for git operations to trigger CI on bot PRs

[leggetter]

Summary

Replace the workflow dispatch approach for triggering CI checks with a token-based solution. When a push_token is provided, use it for git push and PR creation operations so GitHub recognizes events from a real user and automatically triggers pull_request workflows.

Key Changes

• New push_token input: Added optional input parameter that accepts a PAT or GitHub App token for git operations. Falls back to github_token if not provided.
• Git remote authentication: Configure git remote URL with the push token so push operations are authenticated as the token owner, triggering GitHub workflows normally.
• PR creation with push_token: Use the push token when creating PRs via the GitHub API, ensuring the PR creation event triggers pull_request workflows.
• Removed workflow dispatch calls: Deleted the manual workflow_dispatch API calls that previously attempted to trigger the test workflow. This approach is no longer needed when using a proper token.
• Removed actions: write permission: No longer required since we're not dispatching workflows manually.
• Updated documentation: Clarified the new approach in README with setup instructions for the optional AUTO_IMPLEMENT_PUSH_TOKEN secret.

Implementation Details

• The push_token defaults to github_token if not explicitly set, maintaining backward compatibility
• When push_token is set, both git operations and PR creation use it, ensuring consistent authentication
• The solution respects GitHub's restriction on GITHUB_TOKEN not triggering pull_request workflows by using a real user token instead
• Documentation now recommends a classic PAT with repo scope or fine-grained token with contents: write + pull-requests: write

https://claude.ai/code/session_01PHFVduUenioa8nn4NMCabe