Resolve 10 mismatch stubbings in QueryTest.java

[ARMS2025]

We are researchers and analyzed the test doubles (mocks) in the test code of the project. In our analysis of the project, we observed that

• 1 stubbing for the getCapability method is created in QueryTest.initQueryObject and is stubbed with argument
  "platformName", but in actual execution, it is called with argument "automationName", resulting in mismatched stubbings. This mismatch occurred in tests: returnsAValidSelectElement, returnsAValidSelectElement, returnsDefaultLocator, returnsChromeLocatorIfSet, checkAlternateLocatorIsCaseInsensitiveWithUpper, checkAlternateLocatorIsCaseInsensitiveWithLower, returnsWebElement ,returnsWebElementList, findMobileElementThrowsUnsupportedOperationExceptionIfPlatformIsNotAMobileType, findMobileElementThrowsUnsupportedOperationExceptionIfPlatformIsAGenericName,

In this pull request, we propose a solution to resolve the mismatch stubbing.

Mismatched stubbing occurs when a mocked method is stubbed with specific arguments in a test but later invoked with different arguments in the code, potentially causing unexpected behavior. Mockito recommends addressing these issues, (https://www.javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/exceptions/misusing/PotentialStubbingProblem.html)