feat: add TaskiqAdminMiddleware and aiohttp package

[spikeninja]

• add TaskiqAdminMiddleware to middlewares
• add aiohttp package

[s3rius]

I'm not sure if this will work as you intended.

I think it would be better to make all method implementations asynchronous to ensure that the loop is running. While we are pretty much confident that it should execute correctly, it might be somewhat controversial for users who want to test this middleware or use it manually for some reason.

Since TaskiqMiddleware allows you to define both synchronous and asynchronous methods, you can achieve this by simply adding the async keyword right before the def.

What do you think? Does this make sense to you?

[smalyu]

Thanks for #478!
Could you please consider emitting task lifecycle events to the broker (Redis/RabbitMQ) and letting the admin service consume them asynchronously (Celery/Flower style), instead of reporting status via HTTP from workers?
That would remove per-task HTTP overhead, avoid coupling to admin availability, and scale better under load.

[spikeninja]

Hey @smalyu

Yes, I would like to add it but as a separate middleware, smth like TaskqAdminBrokerMiddleware

Let me firstly finish refining the http one pls and we can jump into the broker one)

[spikeninja]

@s3rius Review it pls