Remove retry for unit tests

[duanemay]

From #3229
We want unit tests to be as robust as possible.

Experiment: remove retries, and fix tests.
If it fails too often and is blocking, we can re-introduce retries at the test level with the junit-pioneer @RetryingTest annotation.

[duanemay]

We did see one failure on container-test-job postgresql-16

DeprecatedUaaTokenServicesTests > createAccessTokenRefreshGrantSomeScopesAutoApprovedDowngradedRequest(TestTokenEnhancer) > 1: old behavior FAILED
    java.lang.AssertionError: 
    Expecting actual:
      eyJqa3UiOiJodHRwczovL3VhYS51cmwvdG9rZW5fa2V5cyIsImtpZCI6InRlc3RLZXkiLCJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiIxMjM0NSIsInVzZXJfbmFtZSI6Impkc2EiLCJvcmlnaW4iOiJ1YWEiLCJpc3MiOiJodHRwOi8vbG9jYWxob3N0OjgwODAvdWFhL29hdXRoL3Rva2VuIiwicmV2b2NhYmxlIjp0cnVlLCJjbGllbnRfaWQiOiJjbGllbnQiLCJhdWQiOlsic2NpbSIsImNsaWVudHMiXSwiemlkIjoidWFhIiwiZ3JhbnRfdHlwZSI6ImF1dGhvcml6YXRpb25fY29kZSIsInVzZXJfaWQiOiIxMjM0NSIsImF6cCI6ImNsaWVudCIsInNjb3BlIjpbInJlYWQiXSwiZXhwIjoxNzM3MTk2ODUxLCJpYXQiOjE3MzcxNTM2NTIsImp0aSI6ImY1ZTMzMTk4YWM1MTQ3YmJiNzVlZWIzZDA4ZDZhMmJiIiwiZW1haWwiOiJqZHNhQHZtd2FyZS5jb20iLCJyZXZfc2lnIjoiMzMxNGRjOTgiLCJjaWQiOiJjbGllbnQifQ.RzJfLVva7NznhuS0ORic9Nv0hXvmQyAWibhKFXZms4s
    to be should be valid for <is <43200>>
        at org.cloudfoundry.identity.uaa.oauth.DeprecatedUaaTokenServicesTests.createAccessTokenRefreshGrantSomeScopesAutoApprovedDowngradedRequest(DeprecatedUaaTokenServicesTests.java:982)

[strehle]

I re-run the unit tests 2 additional times... no failure, so good enough to merge...

The bigger problem is in integration test and timeout with simple saml... the 5 sec. timeout is too small