[BUG][Java][Spring] Feign Clients have the same name when multiple tags are specified

Spring generator using the spring-cloud library generates a Feign client for each tag used in the API specification.
However the name on each client is the same, causing an Invalid bean definition with name error on startup, due to the duplicate name.

Settings:

<configOptions>
	<sourceFolder>${generated-sources-java-path}</sourceFolder>
	<java8>true</java8>
	<dateLibrary>java8</dateLibrary>
	<library>spring-cloud</library>
	<useBeanValidation>true</useBeanValidation>
	<performBeanValidation>true</performBeanValidation>
</configOptions>
<generatorName>spring</generatorName>

Example code generated:

@FeignClient(name="${springMicroservice.name:springMicroservice}", url="${springMicroservice.url:http://localhost}", configuration = ClientConfiguration.class)
public interface TagOneApiClient extends TagOneApi {
}

@FeignClient(name="${springMicroservice.name:springMicroservice}", url="${springMicroservice.url:http://localhost}", configuration = ClientConfiguration.class)
public interface TagTwoApiClient extends TagTwoApi {
}

Example error:

Caused by: org.springframework.beans.factory.support.BeanDefinitionOverrideException: Invalid bean definition with name '${springMicroservice.name:springMicroservice}.FeignClientSpecification' defined in null: Cannot register bean definition [Generic bean: class [org.springframework.cloud.openfeign.FeignClientSpecification]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null] for bean '${springMicroservice.name:springMicroservice}.FeignClientSpecification': There is already [Generic bean: class [org.springframework.cloud.openfeign.FeignClientSpecification]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null] bound.

Start at the Spring generator's spring-cloud path and trace how the FeignClient annotation is produced for APIs created from multiple tags. Compare the generated annotations for TagOneApiClient and TagTwoApiClient, then identify an existing generator test area for this output. Done means separately generated clients no longer register the same Feign client name and the behavior is covered by a regression test.