Add a hook point to the Matching service once a task has been matched or not

[02strich]

What changed?

This adds a hook point to the matching service once it has matched a task or decided to spool it.

Why?

This can be leveraged to react to task sync or no-sync match events, while keeping matching service decoupled from the event handling logic.

How did you test it?

• built
• run locally and tested manually
• covered by existing tests
• added new unit test(s)
• added new functional test(s)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}