Support separate consul discovery properties for grpc and http services

Hello! Starting from some version now grpc automatically registers itself on consul. I have TWO registrations now: <service name> and grpc-<service name> both with same set of tags. There is no way I can separate those two by tags or keep only <service name>. The only way is to filter by service name prefix grpc-, which is a very bad practice (what if I want to name my service grpc-something?). Currently I have to use awkward spring.autoconfigure.exclude (which doesn’t concat automatically if specified in several profiles, see https://stackoverflow.com/questions/41170316/combine-list-from-multiple-spring-boot-yaml-files). Here are few suggestions I have:

1. Add a separate setting for enabling grpc consul (and probably other servers) registration. See OnConsulRegistrationEnabledCondition which requires both spring.cloud.service-registry.enabled and spring.cloud.consul.service-registry.enabled flags. We can disable all auto registration or only consul auto registration this way. For grpc you might wanna check both spring.cloud.service-registry.enabled and spring.cloud.grpc.discovery.service-registry.enabled
2. Add grpc service registration tags which override spring.cloud.consul.discovery.tags when applied to grpc service registration like spring.cloud.grpc.discovery.tags
3. Extract grpc- hardcode into config to something like spring.cloud.grpc.discovery.service-prefix

[jvmlet]

@OverDrone , FYI, see #251 , 4.5.8-SNAPSHOT should be published in few minutes

[OverDrone]

Yes, that should do it for me, thx. I don’t require hotfix solution. I can live with spring.autoconfigure.exclude for some time. Take your time to build quality product 😃