Move test files to test/ directory

[keram]

Why: To better separate production code and tests and improve maintainability. h Pros:

• Easier to navigate and write tests for specific modules in isolation
• Simpler idris2 CI workflow
• Follows convention of other popular emacs packages company-mode, cider, haskel-mode..

Cons:

• Nested structure and need to tweak the load path for modules tests being correctly loaded in test/ directory

[jfdm]

Looks like one of the builds aborted for reasons not connected to your PR. I have restarted said build, and one if successfully finishes we can merge.

[keram]

Looks like one of the builds aborted for reasons not connected to your PR. I have restarted said build, and one if successfully finishes we can merge.

One of my ideas for next weeks is to separate API contract tests between Idris and idris-mode out of the actual tests of the idris-mode feature(s). On high level it may consist of defining two separate steps in CI

• First step will run the unit tests against different versions of Emacs with mock Idris server or stubs
• Second step will test and verify that Idris is returning expected responses and potentially may generate also fixtures for the unit tests.

This will lead to reduced CI but also local "random" failures and also improve speed of running tests. (some of the tests take more than 5 seconds which is quite painful too)

[jfdm]

It has aborted again. I shall merge this, as the issue is not the PRs fault.