Event bus internal improvements

[vietj]

See also #4712

Decouple message emission from the interceptor chain

EventBus streaming requires to send messages that does not go through the interceptor chain, e.g. establishing a stream requires to send such messages. The sendOrPub method and the downstream chain of calls (sendLocally, sendOrPublishFailed, sendToNode, sendToNodes) are coupled to OutboundDeliveryContext by convenience. The EventBus#sendOrPub is refactored to carry the messages and the delivery options instead of the OutboundDeliveryContext.

Main changes

• EventBusImpl#sendOrPub(OutboundDeliveryContext) -> EventBusimpl#sendOrPub(ContextInternal,MessageImpl,DeliveryOptions,Promise)
• same for sendLocally, sendOrPublishFailed, sendToNode, sendToNodes

Decouple the RegistrationHandler from the repliedAddress knowledge

The clustered event bus is aware of the nature of the HandlerHolder: when a HandlerHolder is registered it does broadcast the registration when the HandlerHolder is a reply handler. The HandlerHolder#isReplyHandler() method is removed, instead EventBusImpl#addRegistration replaces the replyHandler boolean by a broadcast boolean, when broadcast is set to false the onLocalRegistration method is not called avoiding the clustered event bus to perform the check.

Main changes:

• HandlerRegistration#register(String repliedAddress, boolean localOnly, Promise<Void> promise) -> HandlerRegistration#register(boolean broadcast, boolean localOnly, Promise<Void> promise)
• HandlerHolder does not carry anymore the replyHandler boolean
• MessageConsumerImpl calls register with broadcast = true
• ReplyHandler calls register with broadcast = false
• ClusteredEventBus processes a local registration whatsoever as it is not called for reply handlers

NodeSelector cleanup

The NodeSelector SPI is coupled to event-bus message API, instead it should only care about the message address, this simplifies the API and decouple the NodeSelector SPI from the message.

Main changes:

• NodeSelector#selectForSend(Message, Promise<String>) -> NodeSelector#selectForSend(String, Promise<String>)
• etc...

[vietj]

cc @tsegismont , some cleanup required in the PR, just you get the idea of the changes

[tsegismont]

The NodeSelector SPI is coupled to event-bus message API,

It was designed like this so that users can create their own node selector and choose a server depending on metadata provided by messager headers (e..g. implementing sharing on the event bus)

[tsegismont]

Thanks @vietj