feature/CSTACKEX-217: Mockito upgrade for supporting java21,17 and 11

[piyush5netapp]

Description

This PR...

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

Ran UT with different Java versions.
JAVA_HOME=/usr/lib/jvm/java-1.11.0-openjdk-amd64 mvn -pl plugins/storage/volume/ontap/ clean test - PASS
JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64 mvn -pl plugins/storage/volume/ontap/ clean test - PASS
JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64 mvn -T8 -P developer,systemvm clean install -Dnoredist -pl plugins/storage/volume/ontap/ - PASS

How did you try to break this feature and the system with this change?

[Copilot]

Pull request overview

This PR adjusts the ONTAP storage-volume plugin’s Maven test dependency versions to align Mockito with the root build (to better support running tests on newer JDKs like Java 21), and updates the Byte Buddy agent version used by tests.

Changes:

• Switch ONTAP plugin Mockito dependencies to use the root ${cs.mockito.version} instead of module-local Mockito properties.
• Bump byte-buddy-agent test dependency version to 1.15.11.
• Remove the module’s mockito-inline dependency and remove an explicit skipTests=false configuration entry.

Comments suppressed due to low confidence (1)

plugins/storage/volume/ontap/pom.xml:120

• Mockito.mockStatic(...) is used in this module's tests (e.g., OntapPrimaryDatastoreProviderTest), but the POM no longer includes mockito-inline. Without the inline mock maker, static mocking will fail at runtime (Mockito will throw that the current MockMaker doesn't support static mocks). Re-add mockito-inline as a test dependency (or provide a mockito-extensions/org.mockito.plugins.MockMaker resource enabling mock-maker-inline).

        <!-- Mockito -->
        <dependency>
            <groupId>org.mockito</groupId>
            <artifactId>mockito-core</artifactId>
            <version>${cs.mockito.version}</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.mockito</groupId>
            <artifactId>mockito-junit-jupiter</artifactId>
            <version>${cs.mockito.version}</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>net.bytebuddy</groupId>
            <artifactId>byte-buddy-agent</artifactId>
            <version>${byte-buddy-agent.version}</version>
            <scope>test</scope>
        </dependency>

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sandeeplocharla]

Let's align <maven-surefire-plugin.version>, <assertj.version> and <junit-jupiter.version> versions also with the root pom.xml for now.

[piyush5netapp]

These are independent libraries from Mockito. They can be taken up later as part of internal upgrade story.

[suryag1201]

no need to add this dependency explicitly. it should come with Mockito-core itself. Could u please check this once