Use configKey instead openApiSpecId on template

[mcruzdev]

Many thanks for submitting your Pull Request :heart:!

Fixes #554.

Please make sure that your PR meets the following requirements:

• [x] You have read the contributors guide
• [x] Your code is properly formatted according to our code style
• [ ] Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
• [x] Pull Request contains link to the issue
• [ ] Pull Request contains link to any dependent or related Pull Request
• [ ] Pull Request contains description of the issue
• [ ] Pull Request does not include fixes for issues other than the main ticket

How to backport a pull request to a different branch?

In order to automatically create a **backporting pull request** please add one or more labels having the following format `backport-`, where `` is the name of the branch where the pull request must be backported to (e.g., `backport-quarkus2` to backport the original PR to the `quarkus2` branch). > **NOTE**: **backporting** is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another. Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added. If something goes wrong, the author will be notified and at this point a manual backporting is needed. > **NOTE**: this automated backporting is triggered whenever a pull request on `main` branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

[hbelmiro]

@mcruzdev can you please rebase so it can pass the CI?

[github-actions[bot]]

🎊 PR Preview cfc6fa8ac36cbab8fb708adaae0c25af373766b8 has been successfully built and deployed. See the documentation preview: https://quarkus-openapi-generator-preview-pr-598.surge.sh