#24801 [Java][Spring] Adding example parameter in @Schema annotation for OAS 3.1

Added logic so when multiple examples exist in 3.1 spec, they are generated int he corresponding @Schema notation and can be referenced as needed.

Serves as a fix for #24755

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

Renders OpenAPI 3.1 examples values into the @Schema annotation for Java Spring generators, fixing #24755.

New Features

• Adds examples parameter support to @Schema when the spec declares multiple example values; single values render as a one-element array and properties without examples are unchanged.