Refactored querying RabbitMQ query status from RabbitMQ admin api

[Hilbrand]

This changes the way the scheduled RabbitMQ admin api is queried to get the latest stats on queries. It used to query per worker queue, but this change queries the data for all queues at once.
This will make it easier to also get status on all client queues. This change is in preparation to create telemetry metrics on client queues.
To keep things simple the changes for client queue metrics is not included in this pr.
Most of the changes in the pr are due to using a record to pass the states instead of the individual values to methods. It also changes the frequency the api is queried to 10 seconds. It was 60 seconds, but it did that for each worker queue. With this change it only needs 1 call and we'll get slightly more detailed data by querying a bit more often.
With this change the event based update of channels state triggered by RabbitMQ events has been removed, as the new 10 seconds update fast enough to handle changes.

[SerhatG]

is the difference between getWorkerQueueState() and getWorkerQueueStates() that the latter is used to fetch them all (so every 20 seconds).. and first former to update it when we get an event from the event_exchange plugin, letting us know the amount of consumers changed?

If that's the case I would be open to simplify taskmanager a bit and simply fetch all queues every 10 seconds and use that and get rid of the events_exchange.. Or did we use it for other purposes as well?

[Hilbrand]

@SerhatG Yes that is how it works. The event_exchange is also only used here.
My first version had actually implemented it with this removed (not yet all code was removed, only the update call) and the 10 seconds update. But when testing I noticed the startup had some lagging to detect the changes, therefore I put it back. However, this is basically only a little inconvenience when developing and not really an issue on a production system. So yes it will make it cleaner if removed. I'll remove it.

[BertScholten]

LGTM, just 1 check question about test data