Disable groovy client tests

Disable groovy test due to the following errors in the server side:

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'groovy'.
> Could not resolve all artifacts for configuration ':classpath'.
   > Could not resolve org.jfrog.buildinfo:build-info-extractor-gradle:2.0.16.
     Required by:
         project :
      > Could not resolve org.jfrog.buildinfo:build-info-extractor-gradle:2.0.16.
         > Could not get resource 'https://repo.jfrog.org/artifactory/gradle-plugins/org/jfrog/buildinfo/build-info-extractor-gradle/2.0.16/build-info-extractor-gradle-2.0.16.pom'.
            > Could not GET 'https://www.jfrog.com/error?from=repo.jfrog.org&by=nginx-dedicated2e'. Received status code 403 from server: Forbidden

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

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 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh

  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*. For Windows users, please run the script in Git BASH.
• File the PR against the correct branch: master (5.3.0), 6.0.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.