Queue and Worker Registry

[tyt2y3]

ComponentRegistry has to be in scope when Queue and Worker are derived, in which they will automatically be registered to it.

Then on runtime we can use ComponentRegistry::build_config to construct the config object.

This removes the need to manually register and thus wouldn't "forget" about them.

INFO oxanus::registry: Registering foo::QueueThrottled
INFO oxanus::registry: Registering foo::QueueTwo
INFO oxanus::registry: Registering foo::QueueOne
INFO oxanus::registry: Registering foo::WorkerInstant2
INFO oxanus::registry: Registering foo::WorkerInstant
INFO oxanus::registry: Registering foo::Worker2Sec
INFO oxanus::registry: Registering foo::Worker1Sec
INFO oxanus::launcher: Starting worker (namespace: oxanus)

[tyt2y3]

ComponentRegistry is a unique type owned by user's crate.

Each ComponentRegistry is unique, and would only contain types that's registered to it statically.

The derive macros generate register_component!(ComponentRegistry, TestWorker) under the hood.

[tyt2y3]

On runtime, build_config would iterate all queues and workers and build the config object.

Manual register is no longer needed.

[tyt2y3]

this is the best minimal example