Marking required path parameters as @NotNull

[GregDThomas]

This fixes #21921 by marking required path parameters as @NotNull

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• 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.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@cachescrubber (2022/02)
@welshm (2022/02)
@MelleD (2022/02)
@atextor (2022/02)
@manedev79 (2022/02)
@javisst (2022/02)
@borsch (2022/02)
@Zomzog (2022/09)
@martin-mfg (2023/08)

[wing328]

thanks for the PR

do we need the {{#required}} ... {{/required}} check given that path parameters are always required?

[GregDThomas]

Yeah, that makes a lot of sense now you say it! I’ll get to that as soon as I’m online properly.

[wing328]

thanks for the PR
which has been merged

[GregDThomas]

Thank you :)

[kolomanschaft]

Adding/Removing validation constraints is a breaking change. If the implementing controller does not match the constraints configuration, that causes runtime errors. I would have saved this one for a major release. Plus, you changed it only for the spring Java generator. All other 15 Java/Kotlin generators behave the old way.

[wing328]

Merged #23096 to add an option additionalNotNullAnnotations to include additional @NotNull annotations