Upgrade GitHub Actions to latest versions

[salmanmkc]

Summary

Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.

Changes

Action	Old Version(s)	New Version	Release	Files
actions/create-github-app-token	v1	v2	Release	auto-response.yml, labeler.yml
gradle/actions/setup-gradle	v4	v5	Release	ci.yml

Why upgrade?

Keeping GitHub Actions up to date ensures:

• Security: Latest security patches and fixes
• Features: Access to new functionality and improvements
• Compatibility: Better support for current GitHub features
• Performance: Optimizations and efficiency improvements

⚠️ Breaking Changes

• gradle/actions/setup-gradle (v4 → v5): Major version upgrade — review the release notes for breaking changes
• actions/create-github-app-token (v1 → v2): Major version upgrade — review the release notes for breaking changes
  • ⚠️ Input app-id is now required (was optional) — ensure it is set in your workflow
  • ⚠️ Input private-key is now required (was optional) — ensure it is set in your workflow
  • ⚠️ Input app_id was removed — if your workflow uses it, the step may fail
  • ⚠️ Input private_key was removed — if your workflow uses it, the step may fail
  • ⚠️ Input skip_token_revoke was removed — if your workflow uses it, the step may fail

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.