Adjustments to CI

[ehildenb]

As per thread: https://runtimeverification.slack.com/archives/CC360GUTG/p1648673575711919

• Should not run Integration Tests on GitHub provided runners, which provide very few VCPUs. Perhaps move to self-hosted runners: https://github.com/runtimeverification/devops/issues/46
• Quiet down the performance measurements, not needed for every commit.
• Why do integration tests start so late? Can they start at the same time as unit tests?

[ana-pantilie]

Thanks for opening this!

[F-WRunTime]

This will require further debugging a simple pointer to self hosted runners results in numerous failures some appear to be dependency driven.
First Attempt to Test

[F-WRunTime]

@ana-pantilie are we addressing this issue with our recent work in performance profiling capabilities?

Going forward if we want to run tests on an unhindered hardware
12 Cores 30 GB Mem -- this is the rv-master specs of our github-runner-1 used for performance profiling.

[ana-pantilie]

This is a different kind of "profiling". Here we would like to test run times between different commits on the backend, on some test suites, in order to avoid performance regressions.