Colon (port) in docker registry URI brokes detection of WWW-Authorization URL in DockerConfigJsonSecretToRegistryConfigurationConverter

[Nirvandil]

Description:
Hi there.
I'm using scdf in k8s.
Having something like this in .dockerjson secret
{ "auths": { "registry.somedomain.com:5050": { "username": "kubernetes-puller", "password": "somePassword" } } }
leads to org.springframework.cloud.dataflow.container.registry.authorization.DockerConfigJsonSecretToRegistryConfigurationConverter#getDockerTokenServiceUri fail to detect right URL.
Especially, it passes registry.somedomain.com:5050 (with port!) as host variable to UriComponentsBuilder, so later it detected as IPv6 address in URI.java:

which leads to adding brackets to the URI and then (on build URI) throwing exception because it's invalid IPv6 address obviously. This exception then is swallowed here org/springframework/cloud/dataflow/container/registry/authorization/DockerConfigJsonSecretToRegistryConfigurationConverter.java:212 silently returning Optional.empty().
Release versions:
2.9.6
Steps to reproduce:
Just add custom docker registry with port in his address and see DockerConfigJsonSecretToRegistryConfigurationConverter detects it as basicauth instead of dockeroauth2

[corneil]

@Nirvandil We've identified this is a bug and we will need to ensure the name is handled properly.

[onobc]

Closed via 167132d