feat: use GitHub Actions environments in generated CI/CD workflows

[Copilot]

Fixes #297

Generated CI/CD workflows used environment-specific secret name suffixes (_PROD, _STAGE) to differentiate credentials. This approach should be replaced with GitHub Actions environments, which scope secrets natively per environment.

• Doc PR docs: update CI/CD GitHub Actions guide to use environment-scoped secrets AdobeDocs/app-builder#550

Changes

• deploy_prod.yml — added environment: production to the deploy job; stripped _PROD suffix from all secrets
• deploy_stage.yml — added environment: stage to the deploy job; stripped _STAGE suffix from all secrets
• pr_test.yml — added environment: stage to the test job; stripped _STAGE suffix from all secrets
• Tests — updated assertions to verify environment declarations are present and old suffixed secret references are absent

Before / After

# Before
deploy:
  name: Deploy to Prod
  runs-on: ${{ matrix.os }}
  # ...
  CLIENTID: ${{ secrets.CLIENTID_PROD }}

# After
deploy:
  name: Deploy to Prod
  runs-on: ${{ matrix.os }}
  environment: production
  # ...
  CLIENTID: ${{ secrets.CLIENTID }}

Secrets with identical names are now configured once per GitHub Actions environment (production / stage) rather than duplicated under different names in the same repository secret store.

[github-actions]

🤖 PR Reviewer

This diff refactors GitHub Actions workflows to use GitHub Environments (production/stage) with environment-scoped secrets instead of environment-suffixed secret names. The approach is valid and leverages GitHub's built-in environment protection rules. Tests are updated accordingly and cover the key changes well.

✅ LGTM! This PR looks good to merge.

---

💡 How to re-trigger

Comment /review or /pr-reviewer on this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Superseded by new review

[github-actions]

🤖 PR Reviewer

This diff refactors GitHub Actions workflows to use environment-scoped secrets via GitHub Environments (production/stage) instead of environment-suffixed secret names. The change is clean, well-tested, and follows GitHub best practices for environment-specific secrets. The addition of environment protection rules is a security improvement as it enables required reviewers and deployment gates.

✅ LGTM! This PR looks good to merge.

---

💡 How to re-trigger

Comment /review or /pr-reviewer on this PR