Switch Spring integration workflow from Maven to Bazel

[Copilot]

Spring integration CI was still using Maven, diverging from the repository’s Bazel-based build/test path. This updates the spring GitHub Actions workflow to run Spring + Spring AOT integration builds/tests via Bazel targets.

• Workflow execution model

  • Replaced Maven test invocation with Bazel build/test steps scoped to Spring integration targets.
  • Added Bazel dependency pinning step (@maven//:pin) to keep external resolution aligned with MODULE.bazel.

• Runner/tooling setup

  • Added Bazelisk installation in the workflow job.
  • Set BAZELISK_SKIP_VERSION_CHECK=1 in job env for consistent CI execution.

• Caching strategy

  • Replaced Maven local-repo cache with Bazel disk/repository cache paths.
  • Updated cache keys to track Bazel-relevant inputs (MODULE.bazel, .bazelversion, maven_install.json) and Java matrix version.

- name: Build Spring integrations with Bazel
  run: >-
    bazel build --config=ci
    //spring:client-java-spring-integration
    //spring-aot:client-java-spring-aot-integration

- name: Test Spring integrations with Bazel
  run: >-
    bazel test --config=ci
    //spring:tests

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Copilot
Once this PR has been reviewed and has the lgtm label, please ask for approval from brendandburns. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[brendandburns]

@copilot modify the cache key so it is the same as other CI/CD so that it re-uses builds from the main build/test runs.

[Copilot]

@copilot modify the cache key so it is the same as other CI/CD so that it re-uses builds from the main build/test runs.

Updated in 6c67e4b: the Spring workflow cache key and restore-key prefix now match the main Bazel CI format (bazel-${{ runner.os }}-java${{ matrix.java }}-...) so it can reuse the same cache entries.