[cli][gradle] Validate now uses parseOptions w/setResolve

The validate command now uses ParseOptions#setResolve(true) to match how we parse in CodegenConfigurator and online's Generate. Without this option, the OpenAPI 3 parser skips the "resolve" block, which made lead to validations in the command not matching validations during generation.

I found this difference while stepping through #5413

This will now match: https://github.com/OpenAPITools/openapi-generator/blob/b0b46d57e07696932038122aec569905c5ed5a22/modules/openapi-generator/src/main/java/org/openapitools/codegen/config/CodegenConfigurator.java#L453-L455

and:

https://github.com/OpenAPITools/openapi-generator/blob/b0b46d57e07696932038122aec569905c5ed5a22/modules/openapi-generator-online/src/main/java/org/openapitools/codegen/online/service/Generator.java#L95-L105

PR checklist

• Read the contribution guidelines.
• If contributing template-only or documentation-only changes which will change sample output, build the project before.
• Run the shell script(s) under ./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).
• File the PR against the correct branch: master, 4.3.x, 5.0.x. Default: master.
• Copy the technical committee to review the pull request if your PR is targeting a particular programming language.

cc @OpenAPITools/generator-core-team