feat(java): fix integration test failure

[ex172000]

Which issue does this PR close?

Closes #2702

Rationale

For more stable Java test runs locally

What changed?

Integration tests should not just directly use the 8090 port, instead it should get the random port mapped from 8090 with Testcontainers. This change fixed the failed test by 1) adding the missing class extension 2) getting the random port to create the client..

Local Execution

• Passed ./gradlew test
• Pre-commit hooks ran

AI Usage

1. Which tools? (e.g., GitHub Copilot, Claude, ChatGPT)

• Codex

3. Scope of usage? (e.g., autocomplete, generated functions, entire implementation)

• AI is used for identifying the issue and proposing the initial fix.

5. How did you verify the generated code works correctly?

• The test is ran to ensure the fix is actually working
• Invalid/unnecessary changes are removed from the initial draft and still ensured fix working

6. Can you explain every line of the code if asked?

• Yes

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.31%. Comparing base (db105dd) to head (15a55f5).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #2703      +/-   ##
============================================
- Coverage     68.65%   68.31%   -0.35%     
+ Complexity      637      585      -52     
============================================
  Files           734      734              
  Lines         59764    59764              
  Branches      56177    56177              
============================================
- Hits          41031    40826     -205     
- Misses        16727    16953     +226     
+ Partials       2006     1985      -21     

Flag	Coverage Δ
java	46.08% <ø> (-5.33%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 8 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.