Flexible test configs #73

So I was thinking what could be the next feature (apart from the optimizations) and we could finally dig into the alerting levels and tests that don't run on PRs.

Both can be handled by passing a config object into a test or group of tests (how hard it would be in vitest?) that would tell the test if it should run and what to do next.

By default it could look like:

{
runWhen: {
"daily": true,
"hourly": true,
"onPr": true
},
"alerts": {
"slack": true
}
}

The run when and slack could be completely separate and injected at different times if needed. Then we can create more values, like big performance tests running weekly, on call alerting etc.

What do you think @oklinov @ruocco-l ?