fix: add contents:write permission to workflows with git push operations

[Copilot]

This PR fixes minimum token permissions for GitHub Actions workflows that perform git push operations by adding the required contents: write permission.

Changes Made

1. .github/workflows/release-please.yml

• Added contents: write # required for pushing changes to job-level permissions
• Required for the git push operation on line 62 that pushes package-lock.json updates

2. .github/workflows/update-otel-deps.yaml

• Added new permissions section with contents: write # required for pushing changes
• Required for two git push operations:
  • Line 31: git push origin main --force (sync with upstream)
  • Line 50: git push --set-upstream origin feat/update-otel-deps --force (push feature branch)

Technical Details

Both workflows previously had contents: read at the global level, but GitHub Actions requires contents: write permission specifically for jobs that perform git push operations. The changes:

• Add job-level permissions that override the global contents: read
• Maintain existing permissions (e.g., id-token: write in release-please.yml)
• Include the required trailing comment as specified in the issue

Verification

• ✅ Found exactly 2 workflows with git push operations
• ✅ Both workflows now have proper contents: write permissions
• ✅ YAML syntax validated for both files
• ✅ Minimal changes: 3 lines added, 0 deleted

Fixes #30.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.