GEODE-10551: Update GitHub Actions workflows to trigger on support/2.…

[JinwooHwang]

Description

This PR updates the GitHub Actions workflow files on the support/2.0 branch to enable automated CI/CD checks for pull requests targeting this branch.

Currently, the workflow files exist on the support/2.0 branch but are configured to run on the develop branch, which means no automated checks are triggered for PRs targeting support/2.0. This change fixes that configuration issue.

Changes Made

• Updated .github/workflows/codeql.yml: Changed branch triggers from develop to support/2.0
• Updated .github/workflows/gradle.yml: Changed branch triggers from develop to support/2.0

Motivation

Similar to the work done in GEODE-10550 for the support/1.15 branch, this ensures that:

• Dependency updates and security fixes submitted to support/2.0 are validated before merge
• Pull requests get automated feedback on build status, tests, and code quality
• Security vulnerabilities are detected through CodeQL scanning
• Consistency is maintained with other support branches

Workflows Enabled

Once merged, the following workflows will automatically run for PRs targeting support/2.0:

gradle.yml:

• Build and compile checks
• API compatibility checks (japicmp)
• Unit tests
• Integration tests
• Acceptance tests
• Distributed tests (WAN, CQ, Lucene, Management, Assembly modules)

codeql.yml:

• Security scanning for Java, JavaScript, Python, and Go
• Weekly scheduled scans (Tuesdays at 22:22 UTC)

Testing

• Verified the workflow file syntax is correct
• Changes follow the same pattern as GEODE-10550 for support/1.15
• Branch references properly updated from develop to support/2.0
• All Java 17 configurations remain intact

Related Issues

• GEODE-10550: Enable GitHub Actions workflows for support/1.15 branch (reference implementation)

For all changes, please confirm:

• Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
• Has your PR been rebased against the latest commit within the target branch (typically develop)?
• Is your initial contribution a single, squashed commit?
• Does gradlew build run cleanly?
• Have you written or updated unit tests to verify your changes?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[sboorlagadda]

LGTM

[JinwooHwang]

Thank you so much for taking your time to review it, @sboorlagadda .