Create Gradle task that runs core integration tests to test API ML during release process

[taban03]

Describe the bug
Currently, there is confusion and redundancy regarding the Gradle tasks used for testing API ML on z/OS. We have two tasks: runAllIntegrationTestsForZoweTestingOnZos and runAllIntegrationTestsForZoweTesting. However, these tasks are not properly documented in the internal documentation and run tests that are not strictly necessary for release testing. For example, they include tests like OIDC, PAT, and some negative tests using unauthorized users, which are often unavailable and dependent on specific setups.

To improve this, we should streamline the process by creating a consistent task to run whenever we need to test a release candidate. This task should include only the core tests that are essential and expected to pass reliably.

[balhar-jakub]

I believe we should use the same test suite for the integration testing of the release and that it would be better to figure out what nad how we need to deploy and configure for all the tests to actually run instead of limiting the cases being run.