Link mutations to tests

[SecretSheppy]

Where possible, it would be beneficial to list the tests that ran each mutation, alongside the status of the mutation after each test was run. It would also be helpful to see the source code for each test.

[SecretSheppy]

I have spent a while thinking about the most effective way to add this into the Marv interface whilst maximizing the user experience as I am really not a fan of the MTE method for this. This is the working concept so far.

Details on the above:

1. Each mutations header would be reworked to include a new button to which opens a menu that pushes up the current interface.
2. A table that lists the mutation or test status after the test was run, the test path or name and is clickable.
3. Clicking a test from the list would display the test source code in this section of the window.

It may also be worth adding in a alternative file tree for tests. Instead, the tests and mutations could be merged into one file tree with new icons for separate test files (this would be better for languages like rust where the tests are in the source files). It could be worth also allowing tests to open the bottom window, but link back to mutations.

[SecretSheppy]

Frameworks that export test covered by/killed by data

The table below lists the subset of currently supported frameworks that would be able to support showing tests for mutations.

Framework	Covered by	Killed by
Infection	✔️	✔️
Major	✔️	❌
Pitest	❌	✔️
Mutant	✔️	❌
mutest-rs	✔️	✔️
stryker-net	✔️	✔️
stryker-js	✔️	✔️
stryker4s	✔️	✔️