Cloud matchers

[rdettai]

Offer out of the box matchers from external datasources (Abuse Feodo Tracker, Pulsedive). The matches are published to an SQS queue by a matcher-client service running on fargate.

📝 Checklist

• All user-facing changes have changelog entries.
• The changes are reflected on vast.io, if necessary.
• The PR description contains instructions for the reviewer, if necessary.

🎯 Review Instructions

Start the review by checking out the new documentation

I have fixed a few issues I encountered along the development of the feature:

• refactored the task lifecycle management into common.py as we have both a vast-server and a matcher-client task now
• re-organized the way docker images are managed: they are now all pushed to the same ECR and we use the tag to distinguish which one is used by which service. This avoids needing to create new repositories for plugins that also need use images (which is the case of the matcher with its matcher client)
• added a VASTCLOUD_TRACE flag to help debugging the CLI (by default the stack traces are hidden)
• fixed the dashboard
• increase the VAST server memory to avoid OOM crashes (most of the cost comes from the CPUs anyway)

[rdettai]

TODO:

• https://github.com/tenzir/event-horizon/pull/1553
• Add integration tests with a fixed Feodo and Pulsedive set of matchers

[rdettai]

https://github.com/tenzir/vast/actions/runs/2851832812

[rdettai]

https://github.com/tenzir/vast/actions/runs/2866002074

[rdettai]

https://github.com/tenzir/vast/actions/runs/2867157815

[rdettai]

@dispanser don't review the docs to harshly, I will actually bring another batch of improvements to it in #2510 😉

[dispanser]

Tested and was able to see matching events in the SQS queue. Thanks!

A remark and a spelling correction in the comments :)