feat(bus): implement EventBus for RabbitMQ

[RomanReznichenko]

closes #5

[codeclimate]

Code Climate has analyzed commit 4cbb1c9 and detected 5 issues on this pull request.

Here's the issue category breakdown:

Category	Count
Complexity	1
Duplication	4

The test coverage on the diff in this pull request is 98.4% (50% is the threshold).

This pull request will bring the total coverage in the repository to 99.0%.

View more on Code Climate.

[derevnjuk]

Please follow this guideline: #1 (comment)

According to BranchByAbstraction you should extract Bus abstraction into a separate PR. The same is true for RetryStategy, make sure that you utilize atomic PRs. while working on huge tasks. How to split huge tasks into small pieces you can find in LLD (see Proposal).

Moreover, Bus implementation should be to be inside a separate bus package according to LLD.

[derevnjuk]

There are a lot of critical issues, oddities, and bugs.

In addition to comments, please pay attention to the following ones:

• As discussed you should use amqp-connection-manager to build robust and reliable transport, or implement auto-reconnect manually as it is done in nexploit-cli. See https://github.com/NeuraLegion/integration-bus
• Rework tests according to comments in feat(core): provide a lightweight and simple way to configure SDK #1 (i.e. AAA pattern, proper expectations, an assertion for the whole result of execution, etc)
• SdkConfig and EventBusConfig are separate entities. You should separate them.
• Fix spelling and grammar mistakes in the test titles.

[derevnjuk]

@RomanReznichenko please ensure 100% test coverage of RMQEventBus. BTW it seems you forgot to implement HttpCommandDispatcher (you can start working on it in a separate PR)