Figure out what to do with msys2-runtime tests in this repo

[lazka]

It has a copy of the convert code and a bunch of tests.

Suggestion:

• Make sure the code is in sync with the runtime
• Test against the real runtime somehow, if all fails via a dummy mingw binary that just prints all args and env vars back Start some path conversion integration tests #21
• Move the testing code to https://github.com/msys2/msys2-tests, so we run it more often, against staging, and can potentially add more runtime tests Integrate path_convert tests #22
• Archive this repo

[lazka]

It was suggested that we could also make them into unit tests in msys2-runtime. I still think having some integration tests in msys2-tests is still a good idea never the less.

[dscho]

I would love for these tests to be integrated into the msys2-runtime repository. And I agree that the tests would also make sense to be run in the daily msys2-tests runs

One option would be to use this here repository as a submodule for both. But. You know. Submodules. Friends don't let friends use submodules.

Another option I thought about would be to use git subtree. Essentially, this would "merge path_convert into a subdirectory of msys2-runtime.

The option I like best, I think, at least at this moment, is to move the code into msys2-runtime (probably using a singleton git subtree call), archive this here repository, and use a partial clone of msys2-runtime in msys2-tests.

Whatever option we'll end up using, I think we need to consider the consequences well. I, for one, would like to think about this for a while.

[lazka]

I've moved the relevant code plus this issue to https://github.com/msys2/msys2-tests now, as an intermediate step.