Fix panic when response failed by timeout

[yurahaid]

Fix Panic on Response Timeout in handleWriteWithResponse

When it happened:

1. You declare a publisher, but for some reason, the response from the RabbitMQ is delayed
2. handleWriteWithResponse handle timeout and remove response from coordinator
3. Delayed response arrived from Rabbitmq into handleGenericResponse, but GetResponseById can't find the response because it was deleted in step 2, and we got a panic

[hiimjako]

LGTM

@Gsantomaggio, shouldn't this logic apply to all message types? Currently, sometimes errors are only logged, while other times they are logged and the function returns without sending.

[yurahaid]

I agree with @hiimjako.
I think if we get an error from c.coordinator.GetResponseById(readProtocol.CorrelationId), we should always avoid using Response because it will be nil`

If you're ok with it, I will add a new commit to the current PR to fix it.

[Gsantomaggio]

If you're ok with it, I will add a new commit to the current PR to fix it.

Yes. Thank you.

[Gsantomaggio]

Thank you @yurahaid and @hiimjako for the review