[WIP] Introduce universal compilation host to execution framework

[erak]

Description

This PR implements a universal compiler host for running tests with various compilers (etc. the internal compiler aka. CompilerStack or standard JSON compiler).

Details

It introduces some common types for the compiler inputs and its output. A compilation module that wraps the linked / internal compiler was added. It can be used in a newly added universal compiler host. This host is then used inside the test execution framework.

Outlook

The input / output types introduced by this PR were inspired by the SolidityCompilationFramework. In a future PR the universal compiler host could be used there as well.

Ultimately, this PR makes it possible to implement a compilation module for the standard JSON compiler as well and use that in the pipeline.

TODO

• fix remaining end-to-end tests
• use std::map instead of std::vector to store compiled contracts in the output
• move function definitions to .cpp files
• replace solAssert by soltestAssert

[github-actions]

Thank you for your contribution to the Solidity compiler! A team member will follow up shortly.

If you haven't read our contributing guidelines and our review checklist before, please do it now, this makes the reviewing process and accepting your contribution smoother.

If you have any questions or need our help, feel free to post them in the PR or talk to us directly on the #solidity-dev channel on Matrix.

[cameel]

This is weird. I rebased this to get the tests to run (I thought they didn't run originally because the PR is from a fork and maybe out of CCI credits) but they all fail across the board during checkout. Apparently due to permissions to the repo?

[ekpyron]

@erak (once you're back): you should have permissions to post branches in the main repo, that should make CI more well-behaved (I think when there's several CI subscriptions involved or such, there's weird issues otherwise)