Consider consolidating triage-ops and triage-serverless into this project

In triage-ops!952 (merged), I'm using almost the same code for a non-reactive policy as from a reactive policy: !171 (merged).

It made me realize that, reactive and non-reactive policies can be very similar when their "actions" are defined in Ruby.

If we'd have a single triage-ops project that handle both reactive and non-reactive policies, we could share such Ruby classes.

Also, from the perspective of someone outside of the team, it just makes more sense to have a single triage-ops project to contribute to.

Having a single project would also be a step forward #62 (moved).