[Java] [VertX] Handle hyphen-separated security schemes in input spec

[rohitsanj]

resolves #18629

Add lambda call to camelcase to correctly handle hyphen separated security schemes when generating the AuthInfo class in Java vertx client.

Steps to validate this branch:

1. Checkout to this branch locally and build the JAR: ./mvnw clean package
2. Run the following command:

   java -jar modules/openapi-generator-cli/target/openapi-generator-cli.jar \
   generate \
   -g java \
   --library vertx \
   -o /var/tmp/java-vertx-client-test \
   -i https://gist.githubusercontent.com/rohitsanj/bd1f1f6747c41299bf4ce714ec2cda80/raw/6d46a2cfe8cf2dc173099e2b041af4dccb29c54a/openapi.yaml
   

3. After generating the project with the steps above, navigate to src/main/java/org/openapitools/client/ApiClient.java and verify that there are no syntax errors in the AuthInfo class.

I've also added a unit test to prove the fix.

Tagging openapi-generator Java committee explicitly (as mentioned in the PR checklist): @martin-mfg

PR checklist

• [x] Read the contribution guidelines.
• [x] 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.
• [x] 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.
• [x] File the PR against the correct branch: master (upcoming 7.1.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• [x] If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.