[REQ-22001][FIX] Add MCP server support to apiService.mustache

[thibautrety]

Refactor apiService.mustache to include MCP server support and enhance operation methods.

The goal is to directly generate a MCP server in quarkus.

Two extensions are used :

x-enable-mcp-server : (default is false) at the root of the spec, states that mcp server is enabled. It should be set to true in order to be enabled
x-enable-mcp-operation : (default is false) On each operation that should be accessible from MCP clients. It states if an specific operation can be accessible from MCP client
The main intent is to transform our REST APIs as GEN-AI ready APIs.

Known Limitations

UUID in parameters ar not supported yet
SecurityContext parameters is not supported yet
See also

An example of usage can be found here : https://github.com/thibautrety/quarkus_mcp/tree/main

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.

[thibautrety]

Hello @wing328 , I have fixed the issue and asked for a new merge request here.
I don't exactly know the procedure but I hope that it's fine

[wing328]

can you please resolve the merge conflicts or file a new PR based on the latest master of the official repo?

[thibautrety]

Thanks for your review.
I'll try to do it tomorrow

[wing328]

closed via #22558 with resolved merge conflicts and updated samples