Make URL creation more robust in Bomr's version resolver

Using URI#resolve is brittle as the behavior changes depending on
whether or not the URI ends with a /. This can result in the
original URI's path being lost and the URLs for the Maven metadata
files being incorrect.

See gh-42333

buildSrc/src/main/java/org/springframework/boot/build/bom/bomr/MavenMetadataVersionResolver.java

@@ -43,6 +43,7 @@ import org.springframework.http.HttpStatus;
 import org.springframework.http.converter.StringHttpMessageConverter;
 import org.springframework.web.client.HttpClientErrorException;
 import org.springframework.web.client.RestTemplate;
+import org.springframework.web.util.UriComponentsBuilder;
 
 /**
  * A {@link VersionResolver} that examines {@code maven-metadata.xml} to determine the
@@ -76,7 +77,10 @@ final class MavenMetadataVersionResolver implements VersionResolver {
 
 	private Set<String> resolveVersions(String groupId, String artifactId, MavenArtifactRepository repository) {
 		Set<String> versions = new HashSet<>();
-		URI url = repository.getUrl().resolve(groupId.replace('.', '/') + "/" + artifactId + "/maven-metadata.xml");
+		URI url = UriComponentsBuilder.fromUri(repository.getUrl())
+			.pathSegment(groupId.replace('.', '/'), artifactId, "maven-metadata.xml")
+			.build()
+			.toUri();
 		try {
 			HttpHeaders headers = new HttpHeaders();
 			String username = repository.getCredentials().getUsername();