v7.25.0 release

[wing328]

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

Finalize 7.25.0 release by replacing all 7.25.0-SNAPSHOT references with 7.25.0 across the root and module builds. Previously artifacts built as snapshots; now they are pinned for publishing with no functional changes.

• Verify root POM and all module/sample build files reference 7.25.0 (including openapi-generator, openapi-generator-cli, openapi-generator-maven-plugin examples, openapi-generator-gradle-plugin properties/samples, openapi-generator-mill-plugin properties, and openapi-generator-online). Ensure no remaining “-SNAPSHOT”.
• Rollout: tag v7.25.0 and publish org.openapitools artifacts; downstream users should depend on 7.25.0 for the CLI and plugins.

^{Written for commit 851ac4b. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 16 files

_{Re-trigger cubic}