feat: extented RMQ features

[Lancetnik]

Description

Close #1318, close #975

Type of change

Please delete options that are not relevant.

• Documentation (typos, code examples, or any documentation updates)
• Bug fix (a non-breaking change that resolves an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a fix or feature that would disrupt existing functionality)
• This change requires a documentation update

Checklist

• My code adheres to the style guidelines of this project (scripts/lint.sh shows no errors)
• I have conducted a self-review of my own code
• I have made the necessary changes to the documentation
• My changes do not generate any new warnings
• I have added tests to validate the effectiveness of my fix or the functionality of my new feature
• Both new and existing unit tests pass successfully on my local environment by running scripts/test-cov.sh
• I have ensured that static analysis tests are passing by running scripts/static-analysis.sh
• I have included code examples to illustrate the modifications

[pythrick]

@Lancetnik great to see there's an implementation for reusing RabbitMQ connections with aio_pika.Pool. Is there an idea when it will be merged? Thank for you amazing job.

[Lancetnik]

@Lancetnik great to see there's an implementation for reusing RabbitMQ connections with aio_pika.Pool. Is there an idea when it will be merged? Thank for you amazing job.

Sorry, but I had to love priority
I'll continue to work on it after 0.6.0 in a few months

[pythrick]

Thank you!

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Lancetnik
❌ Focadecombate
_{You have signed the CLA already but the status is still pending? Let us recheck it.}