fix: updated dedupe to check history of sent packets

[mvandevalk]

Updated the dedupe function to checks if a packet has already been seen before, based on the packet's broker ID and counter. If the packet is a duplicate (already seen before), it is not forwarded again. The temporary list for dedupe is configurable as part of the init options, defaults to 100.

This bug occurs with a mongoDB persistence configuration and have not been able to reproduce with a default persistence settings.

Fixes #955

[mcollina]

Thanks for opening a PR! Can you please add a unit test?

[coveralls]

Pull Request Test Coverage Report for Build 10404669588

Details

• 12 of 12 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.002%) to 99.745%

---

Totals
Change from base Build 9447929816:	0.002%
Covered Lines:	832
Relevant Lines:	832

---

💛 - Coveralls

[robertsLando]

@mvandevalk I think this should be fixed on mongo persistence instead, if this happens it means the packets are not processed in the correct order. The way dedupe works is good as it increments the brokerCounter every time a packet is processed so it can skips packets with an old broker counter