Remove bug label from workflow test failures

[brooke-hamilton]

Description

This pull request includes changes to the GitHub Actions workflows to update the labels used when creating issues for failed jobs. The changes involve removing the 'bug' label from the issues created by various workflows.

⚠️ There is no way to test these workflows from a fork. However, I did run the workflow step below in a private repo to create issues.

      - name: Create GitHub issue
        uses: actions/github-script@v7
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          script: |
            github.rest.issues.create({
              ...context.repo,
              title: `Scheduled functional test failed - Run ID: ${context.runId}`,
              labels: ['test-failure'],
              body: `test failure.`
            })

Label updates in issue creation:

• .github/workflows/functional-test-cloud.yaml: Removed the 'bug' label from issues created when the scheduled functional test fails.
• .github/workflows/functional-test-noncloud.yaml: Removed the 'bug' label from issues created when the scheduled functional test (noncloud) fails.
• .github/workflows/long-running-azure.yaml: Removed the 'bug' label from issues created when the scheduled long running test fails.
• .github/workflows/purge-aws-test-resources.yaml: Removed the 'bug' label from issues created when the purge AWS test resources workflow fails.
• .github/workflows/purge-azure-test-resources.yaml: Removed the 'bug' label from issues created when the purge Azure test resources workflow fails.
• .github/workflows/purge-old-images.yaml: Removed the 'bug' label from issues created when the purge old images workflow fails.

Type of change

• This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional).

Fixes: N/A

Contributor checklist

Please verify that the PR meets the following requirements, where applicable:

• An overview of proposed schema changes is included in a linked GitHub issue.
  • Yes
  • Not applicable
• A design document PR is created in the design-notes repository, if new APIs are being introduced.
  • Yes
  • Not applicable
• The design document has been reviewed and approved by Radius maintainers/approvers.
  • Yes
  • Not applicable
• A PR for the samples repository is created, if existing samples are affected by the changes in this PR.
  • Yes
  • Not applicable
• A PR for the documentation repository is created, if the changes in this PR affect the documentation or any user facing updates are made.
  • Yes
  • Not applicable
• A PR for the recipes repository is created, if existing recipes are affected by the changes in this PR.
  • Yes
  • Not applicable

[radius-functional-tests]

Radius functional test overview

🔍 Go to test action run

Name	Value
Repository	brooke-hamilton/radius
Commit ref	fb899b8
Unique ID	func21e6719751
Image tag	pr-func21e6719751

Click here to see the list of tools in the current test run

• gotestsum 1.12.0
• KinD: v0.20.0
• Dapr:
• Azure KeyVault CSI driver: 1.4.2
• Azure Workload identity webhook: 1.3.0
• Bicep recipe location ghcr.io/radius-project/dev/test/testrecipes/test-bicep-recipes/<name>:pr-func21e6719751
• Terraform recipe location http://tf-module-server.radius-test-tf-module-server.svc.cluster.local/<name>.zip (in cluster)
• applications-rp test image location: ghcr.io/radius-project/dev/applications-rp:pr-func21e6719751
• dynamic-rp test image location: ghcr.io/radius-project/dev/dynamic-rp:pr-func21e6719751
• controller test image location: ghcr.io/radius-project/dev/controller:pr-func21e6719751
• ucp test image location: ghcr.io/radius-project/dev/ucpd:pr-func21e6719751
• deployment-engine test image location: ghcr.io/radius-project/deployment-engine:latest

Test Status

⌛ Building Radius and pushing container images for functional tests...
✅ Container images build succeeded
⌛ Publishing Bicep Recipes for functional tests...
✅ Recipe publishing succeeded
⌛ Starting corerp-cloud functional tests...
⌛ Starting ucp-cloud functional tests...
✅ ucp-cloud functional tests succeeded
✅ corerp-cloud functional tests succeeded

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.89%. Comparing base (51582ed) to head (fb899b8).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8802      +/-   ##
==========================================
- Coverage   59.89%   59.89%   -0.01%     
==========================================
  Files         595      595              
  Lines       40480    40480              
==========================================
- Hits        24247    24244       -3     
- Misses      14406    14408       +2     
- Partials     1827     1828       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.