JasperFx/wolverine

AI Summary: The task involves improving the consistency of topic and subscription naming in the Wolverine message bus, specifically when using `MultipleHandlerBehavior.Separated` and conventional routing. The current behavior inconsistently uses message or handler types for naming based on the number of handlers, leading to brittle systems. The solution requires either fixing the existing implementation to consistently use message type for topics and handler type for subscriptions, or adding overloads to the routing configuration to allow developers to explicitly define naming conventions using both message and handler types.