fix(nx-quarkus): support javaVersion argument override for nx-quarkus package

[Cameron-C-Chapman]

This tries to address a project generator validation error on the javaVersion argument. Currently when passing javaVersion as an argument you get the error message "Property 'javaVersion' does not match the schema. '17' should be a 'string'.".

This worked when I was on version 8.0.1 of the nx-quarkus plugin, but after upgrading to the latest I started seeing this error.

I couldn't get the dev container setup to work to run the e2e tests and validate the behavior fully.

A couple issues/fixes I saw that seemed relevant that I used to model this change after:

• An issue created in the nx repo that describes string arguments being interpreted as boolean values: Cannot use "--version" as a generator option because it is a reverved word in Yargs nrwl/nx#10786
• A fix for the spring-boot project where a similar issue was reported: https://github.com/nrwl/nx/issues/10786https://github.com/tinesoft/nxrocks/commit/364b22885e74706fd3f6d10323325323439aa2f1

I'd love to be able to get the dev container setup working to be able to contribute to this project more regularly. I'm looking to use it in some critical projects, I may just need a little help/guidance troubleshooting my devcontainer issue. I'm able to run the regular tests, but the verdaccio connection times out when running the e2e tests.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 1fd4752. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 2 targets

• nx affected -t lint test build e2e-ci --parallel=5 --exclude=smoke --codeCoverage
• nx-cloud record -- nx format:check

---

Sent with 💌 from NxCloud.

[tinesoft]

HI @Cameron-C-Chapman

Thank you for spotting the issue and for your pull request, much appreciated.

I'll gladly help you with the issue you're having with the dev container. Let me know more about it (here or via DM)
As for the running the e2e test locally, there do take time indeed (I still need to improve that), but nonetheless you can still
create PRs, and let the CI perform all the e2e tests.