chore: add responded and stale issue/pr workflows

[moorec-aws]

What was the problem/requirement? (What/Why)

Need to standardize issue and PR management workflows across all repositories to automatically handle stale issues/PRs and contributor responses.

What was the solution? (How)

Added two GitHub workflow files:

• responded.yml - Removes stale labels when contributors respond to issues/PRs
• stale_prs_and_issues.yml - Runs hourly to identify and label stale issues/PRs

Both workflows use reusable workflows from the organization's .github repository for consistency.

What is the impact of this change?

• Automated stale issue/PR management
• Consistent labeling behavior across repositories
• Reduced manual maintenance overhead

How was this change tested?

These workflows will be tested automatically when they trigger:

• responded.yml activates on issue comments
• stale_prs_and_issues.yml runs on hourly cron schedule

They have been tested in another repository here:

• https://github.com/aws-deadline/deadline-cloud-for-blender/actions/runs/17332118916

  • Docs: (environment): prerequisite for installing GUI dependencies aws-deadline/deadline-cloud-for-blender#228

• https://github.com/aws-deadline/deadline-cloud-for-blender/actions/runs/17308632537

  • Title: Camera binding ("Bind Camera to Markers") is not respected when "All renderable cameras" option is used or when default camera is locked aws-deadline/deadline-cloud-for-blender#268

Is this a breaking change?

No

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud