Authorization header for uaa needs oauth2 encoding now

UAA changes now to standard oauth encoding:
The RFC for OAuth requires an URL encode in authorization header, see
https://tools.ietf.org/html/rfc6749#section-2.3

The authorization header needs to be
Authorization: Basic base64Encode(urlencode(client_id):urlencode(client_secret))

UAAC does not encode the authorization header. (client)
UAA does not decode the authorization header (server)
Thus this issue does popup in uaac before, however uaac should behave standard conform.

see
https://github.com/cloudfoundry/cf-java-client/blob/master/cloudfoundry-client-reactor/src/main/java/org/cloudfoundry/reactor/tokenprovider/AbstractUaaTokenProvider.java#L185-L187

This will come with UAA-RELEASE 74.0.0, see
https://www.pivotaltracker.com/n/projects/997278/stories/166970393

UAA clients need to be adapted, therefore this issue

Another example:
https://github.com/cloudfoundry/cf-uaac/issues/50

Localisez la requête de jeton UAA et la construction de l’en-tête Authorization dans cf-java-client, puis comparez-les à l’exigence de la RFC 6749 et à l’exemple référencé AbstractUaaTokenProvider.java. La tâche est considérée comme terminée lorsque les informations d’identification du client sont encodées au format URL avant l’encodage Base64 et que le client fonctionne avec UAA-RELEASE 74.0.0.