Are runtime tests actually required in CI??

[paul0403]

Context:
There are a couple different items that seem to be running runtime tests in CI. However it seems like the only entry that runs the full runtime test suite, Runtime Code Coverage, is not actually a required CI item.

Moreover, it seems like the "lightning", "lightning-kokkos" and "openqasm" entries are not actually doing any testing at all.

We slip in a expected failed test into all runtime test files to see which CI entries can pick it up.

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit doc/releases/changelog-dev.md on your branch with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[paul0403]

I don't know how long this has been in there, but apparently none of the required runtime test CI entries right now can actually detect failures! Moreover, the three required runtime test CI entries don't actually run anything!

The only entry that runs the entire runtime test suite is the runtime code coverage, which is not a required CI entry for merging.

This PR slipped a CHECK(1 == 0); into all runtime test files, so if the testing is setup correctly then everything should fail. However, none, other than the runtime coverage, actually failed!