chore(java): update samples

[Mattias-Sehlstedt]

Updates samples after the merge of #23878. Should we remove the generator annotation from these samples to avoid this issue in the future?

PR checklist

• Read the contribution guidelines.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in WSL)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

---

Summary by cubic

Regenerated Java client samples to sync with generator 7.25.0-SNAPSHOT after #23878. Only the @jakarta.annotation.Generated/@javax.annotation.Generated annotation comment in ExceptionProvider was updated; no behavior changes.

^{Written for commit 1617cc5. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 22 files

_{Re-trigger cubic}

[Mattias-Sehlstedt]

Duplicated of b4cb27a