chore: Port core functional logic for Spring Boot 4.0 / Spring Framework 7.0 upgrade

[prathmeshcc]

This PR addresses the core functional changes required to upgrade the project to Spring Boot 4.0 and Spring Framework 7.0. The focus was on surgically resolving compilation failures and breaking API changes while maintaining strict consistency with the project's established Java 8 syntax and formatting conventions.

Key Changes:

• Spring Data 4.0 Migration:

  • Refactored GqlDatastoreQuery and repository lookup strategies to adopt ValueExpressionDelegate.
  • Resolved failures caused by the removal of SpelEvaluator, SpelQueryContext, and QueryMethodEvaluationContextProvider.
  • Updated TypeInformation and PropertyPath imports to the new org.springframework.data.core package.

• Spring Framework 7.0 Refactoring:

  • Aligned HttpHeaders usage in GoogleConfigPropertySourceLocator with the new non-Map API by switching from containsKey() to containsHeader().

• Spring Security 7.0 DSL Update:

  • Migrated security configuration in samples (e.g., spring-cloud-gcp-security-iap-sample) from the deprecated chained fluent API to the modern lambda-based DSL.

• Autoconfigure & Dependency Management:

  • Updated spring-cloud-gcp-autoconfigure to include granular Spring Boot 4.0 modules (e.g., spring-boot-transaction, spring-boot-health).
  • Streamlined pom.xml files to remove redundant version overrides already managed by the Spring Boot 4.0 BOM.

Technical Implementation Details

• Surgical Precision: All changes were applied with minimal diff noise. Deprecated constructor paths were maintained where possible but bridged to new logic to keep the integration clean.
• Build Status: Verified that the project compiles successfully across all modules and samples using ./mvnw clean compile.

Testing Performed

• Executed full reactor build: ./mvnw clean compile -DskipTests -Dcheckstyle.skip -Dfmt.skip.
• Targeted compilation checks for affected modules: Datastore, Spanner, Firestore, and IAP Security sample.

[ldetmer]

this seems like a breaking change, is there a reason why you're removing it?

[prathmeshcc]

The QueryMethodEvaluationContextProvider has been deprecated in Spring Data 2025.01 release notes in favor of ValueExpressionDelegate so we can only support ValueExpressionDelegate.

[ldetmer]

thanks! can you keep track of breaking changes we made to the API so we can include them in the release notes.

Something like:

removed DatastoreQueryLookupStrategy constructor due to spring data removal of QueryMethodEvaluationContextProvider. Users should migrate to DatastoreQueryLookupStrategy

[jinseopkim0]

+1 to @ldetmer's comments

[ldetmer]

removing public methods is a breaking change, is there a reason this has to be removed?

[prathmeshcc]

The QueryMethodEvaluationContextProvider has been deprecated in Spring Data 2025.01 release notes in favor of ValueExpressionDelegate so we can only support ValueExpressionDelegate which means removing this constructor.

[ldetmer]

same here, lets keep track of the breaking changes for release notes

[ldetmer]

i think we can remove since it was already deprecated, but flagging to confirm with @jinseopkim0

[ldetmer]

flag in release notes

[ldetmer]

flagging removal of deprecated method

[ldetmer]

also lets note in release notes