Integration tests are run under the test task

As found in [https://github.com/apache/beam/pull/13308](https://github.com/apache/beam/pull/13308) the [https://github.com/apache/beam/blob/40f517f9da8b2f0914f06493f8e042eeb2739578/sdks/java/extensions/ml/build.gradle#L47-L49](https://github.com/apache/beam/blob/40f517f9da8b2f0914f06493f8e042eeb2739578/sdks/java/extensions/ml/build.gradle#L47-L49) explicitly includes the integration tests in the test task.

As a consequence it is now impossible to run the tests without a google GCP account as the build will fail over missing account information.

Imported from Jira [BEAM-11363](https://issues.apache.org/jira/browse/BEAM-11363). Original Jira may contain additional context.
Reported by: nielsbasjes.

Start with sdks/java/extensions/ml/build.gradle around lines 47-49 and inspect how the integration tests are included in the test task. Run the relevant Gradle test task to reproduce the missing GCP account failure. Done means ordinary tests no longer require GCP credentials, while integration tests remain separately runnable.

Written by the indexing model from the issue text.