Fix operationId mapping

[wing328]

fix operationId mapping using the original operationid

fyi @OpenAPITools/generator-core-team

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 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.

[cbascom]

I like this change since manually converting these names from specs is very annoying :). Any concern with this being a breaking change for anyone that already has configs set up that rely on the old logic though?

[wing328]

Any concern with this being a breaking change for anyone that already has configs set up that rely on the old logic though?

good question.

they can update the mapping names accordingly.

we consider this as a bug fix as all these name mapping options intent to work with the original values provided in the spec.