Reorganize tests

The test suite is currently split between two organization models: some tests are organized by the component, or the feature, they test (like this), and a lot of tests are organized by the number of the GitHub issue they verify (like this).

This leads to test failures due to regressions not being easy to trace, and to some features or behaviors being tested more than once in several different places.

I’d like to reorganize the tests by moving the ones in the io.mockk.gh to the specific package and test class they are related to, possibly adding some more descriptive test names and keeping the association with the GitHub issue in a comment.

This, BTW, also seems to me like a good starting point for new contributors to get accustomed with MockK internals.

[Endhuine]

I totally agree with this. Seems like a huge task, I’ll try to carry on a little by myself, if anyone is interested please, let me know, so we don’t risk doing the same job twice.

[Raibaz]

I think we can consider this completed, since we don’t have any tests named after GitHub issues anymore.

However, there are plenty of issues tagged with good-first-issue that you can start tackling 😃