[Enhancement]: Manage OkHttp versions in xapi-client via BOM to resolve build failures after Spring Boot parent upgrade

[thomasturrell]

What

Adopt the OkHttp BOM in xapi-client/pom.xml to manage versions for com.squareup.okhttp3:okhttp and com.squareup.okhttp3:mockwebserver dependencies. This ensures their versions are consistently managed after upgrading the spring-boot-starter-parent to 3.5.7, which no longer provides transitive version management for these dependencies. The BOM import will restore build stability and improve future dependency maintenance.

Why

This enhancement solves repeated build failures triggered by missing explicit versions for okhttp and mockwebserver following the Spring Boot parent upgrade. By centralizing version management via the BOM, we reduce maintenance friction, avoid hardcoding versions, and ensure better long-term compatibility for dependencies that change versioning policies upstream.

Notes

Apply the following steps:

1. In xapi-client/pom.xml, add/merge the dependencyManagement block importing OkHttp BOM:
   
   com.squareup.okhttp3
   okhttp-bom
   4.11.0
   pom
   import
   
2. Ensure that xapi-client dependencies for okhttp and mockwebserver remain (without ) so they resolve via BOM.
3. Validate with: mvn -B -DskipTests verify

Related context:

• Failure was triggered by Dependabot updating spring-boot-starter-parent to 3.5.7 (see PR Bump org.springframework.boot:spring-boot-starter-parent from 3.3.5 to 3.5.7 #290)
• Error example: 'dependencies.dependency.version' for com.squareup.okhttp3:mockwebserver:jar is missing