Removed 1 unnecessary stubbing in AbstractVaultTokenCredentialWithExpirationTest.java

[ARUS2023]

Testing done

Submitter checklist

Beta Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

In our analysis of the project, we observed that
1 unnecessary stubbing which stubbed getAuthClientToken method in setUp is created but is never executed by 2 tests AbstractVaultTokenCredentialWithExpirationTest.shouldFetchNewTokenIfExpired, AbstractVaultTokenCredentialWithExpirationTest.shouldExpireTokenImmediatelyIfExceptionFetchingTTL.

Unnecessary stubbings are stubbed method calls that were never realized during test execution. Mockito recommends to remove unnecessary stubbings (https://www.javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/exceptions/misusing/UnnecessaryStubbingException.html).

We propose below a solution to remove the unnecessary stubbings.