Test against ci precompiled binaries

[jneira]

• With the lastest releases we can observe that several bugs affecting final users are related with the fact we are offering precompiled binaries and using them by default in the extension/ghcup
• hls developers and ci are testing a version built from source in the same machine so the test suite is green for those bugs
• imo we should run the test suite against the precompiled binaries before make a release, ideally in ci but, at least, locally
  //cc @bubba @alanz

[jneira]

The environment where run that test suite should be a clean one, different from the ci (for example putting ghc in a non standard location and so on)
Maybe circleci could be a good candidate for that environment.

[pepeiborra]

Big thumbs up, this is a must have

[lukel97]

I think I have a branch for this: master...bubba:static-binary-tests
Could be dusted off! It worked by downloading the build artefacts from the previous stage and then running the tests against that. The main change needed to the testsuite was the HLS_TEST_EXE env var so that we could point it to the binary. I might have time soon to look at it, but if anyone else wants to pick it up feel free to

[jneira]

From #2281 (comment) and #2281 (comment)

This could have helped to catch the bug about hs-boot files before releasing 1.5.0

In addition to @bubba suggestion another fuzzy test could be run hls in the cli for some real world projects. The obvious one is hls itlsef as it should be fast cause we have all dependencies in cache. We could choose some other projects known to be problematic.

//cc @pepeiborra