test: transfer aedes tests to the project

[getlarge]

• Fixes [bug] Strange behaviour with retained packets #6

[getlarge]

The current approach is not the most elegant as i duplicated aedes tests inside the codebase to have reliably running tests. Albeit by now i could move those changes back to the local aedes node_modules and trigger patch-package.
The good news is that we can run tap tests with the node:test runner, that's a really great effort!
Another good news is that i know the issue you met is (most probably) related with patchedDeliverFunc, and i'm currently trying to fix it.

[robertsLando]

The good news is that we can run tap tests with the node:test runner, that's a really great effort!

That's so good! 🎉

Another good news is that i know the issue you met is (most probably) related with patchedDeliverFunc, and i'm currently trying to fix it.

Awesome, let me know when this is ready 💪🏼

[getlarge]

Found it.
When subscribing, the delivery function is patched after being passed to Aedes.subscribe and this patched function is then stored by MQEmitter (or rather Qlobber).
When unsubscribing, the delivery function is retrieved from the Subscription - created during handleSubscribe - before being passed to Aedes.unsuscribe and then MQEmitter, to be removed. But this is the original function (not the patched one).
I let you figure out the damage that follows...

It seems like the Subscription has to be patched and then the patched Subscription.func should be passed to Aedes.subscribe.

[robertsLando]

I let you figure out the damage that follows...

Yeah in fact as I said there was some really weird behaviour and this explains it. I think that adding the tests should cover us on almost all this kind of issues 💪🏼