fix: Refactors message decoding to abort as soon as a suitable decoder found

[balag3]

Problem

See the description of the original issue: #1369

Solution

Use Promise.any() instead of tracking the successfully decoded message state (didDecodeMsg)

Notes

• Resolves improvement for decoding messages on filter #1369

npm run fix ok
npm run check ok
npm run test ok

[danisharora099]

looks good - thanks for this!

apologies for the delay in review, the team was mostly away last few weeks
.
pls resolve conflicts and once the CI passes, we'll be happy to merge!

[balag3]

looks good - thanks for this!

apologies for the delay in review, the team was mostly away last few weeks . pls resolve conflicts and once the CI passes, we'll be happy to merge!

No problem at all! Merged and resolved conflicts!

[danisharora099]

Thanks for the PR @balag3 - there were some type errors that were failing the build which I resolved in the above commits.

(For context: there was nothing being returned from inside the map function, which led to the variable having the type of void)

We can merge the PR once the checks pass. Thanks again. We appreciate the support. :)

Cheers!