[java][resttemplate] Fix model combining properties and additional properties

[JoaoBrlt]

When additionalProperties is set to true, use an additionalProperties attribute and @JsonAnySetter and @JsonAnyGetter annotations instead of extending HashMap.

This fixes the issue #17361 only for the resttemplate library.

I also created the following pull requests to fix the same issue for other libraries:

• [java][webclient] Fix model combining properties and additional properties #19711 for the webclient library.
• [java][feign] Fix model combining properties and additional properties #19713 for the feign library.

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 
  ./bin/generate-samples.sh ./bin/configs/*.yaml
  ./bin/utils/export_docs_generators.sh
  

  (For Windows users, please run the script in Git BASH)
  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 is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10) @martin-mfg (2023/08) @wing328

[martin-mfg]

Hi @JoaoBrlt, thanks for the PRs! They look really good. 👍
I'll approve all 3 of them. May I ask you to resolve the conflicts with master?

[JoaoBrlt]

Hey @martin-mfg! 👋 Thanks for approving the pull requests. Yeah, no problem. I'll take a look right now.

[JoaoBrlt]

Hey @martin-mfg! I updated the pull requests to resolve the conflicts with the master branch. ✔️ I redid the modifications using the latest Mustache templates to make sure to benefit from the latest changes. Don't hesitate to tell me if there's any issue.

[JoaoBrlt]

Hey @martin-mfg @wing328! 👋 Do you think we could merge these pull requests for the next version? This would be very useful for my current project. Indeed, we have to manually patch the OpenAPI specs to fix the code generation. I would be happy to help if needed. 😄

[martin-mfg]

Hey @martin-mfg @wing328! 👋 Do you think we could merge these pull requests for the next version? This would be very useful for my current project. Indeed, we have to manually patch the OpenAPI specs to fix the code generation. I would be happy to help if needed. 😄

just for your info: I've done everything I could by approving your PR. :) Now it's up to @wing328 to merge it, because I don't have merge permissions.