add basic CI functionality

[Anton-Latukha]

This is what can be directly ported from HNix OR Haskell-With-Nixpkgs projects.

Nix testing held back because Haskell.Lib API interface can not be ported directly into Store Nix setup. In Nix it is ugly to pass/inherit API through imports, (API passes through essentially by restating API two more times in every file layer).

Thou, Nixpkgs integration test works directly.

In the near future, I going to migrate the Nixpkgs integration test into Haskell-Nix.

[Anton-Latukha]

Now I would change the triggers to run on Push, to test workflows inside the PR.

[sorki]

Neat. I think you can try using cabal.project to add cryptohash-sha512 PR haskell-hvr/cryptohash-sha512#5 temporarily (https://cabal.readthedocs.io/en/3.4/cabal-project.html#specifying-packages-from-remote-version-control-locations).

[Anton-Latukha]

Nixpkgs integration action moved into #89, action code needs some adjustments to support monorepo.

[Anton-Latukha]

#88 (comment) moved into: #90.

[Anton-Latukha]

CI works right.
All situations that are left - are of project code/configuration and do not relate to CI configuration.

ghc: could not execute: tasty-discover - is a project code/configuration situation, over the Internet, there are reports that is a syndrome of internal things.

[Anton-Latukha]

Rolling the action triggers back to what they should from within the master branch.

[sorki]

Maybe you can cabal install tasty-discover

[Anton-Latukha]

It already gets installed by the Cabal during the build.

[Anton-Latukha]

Interesting, nowhere in the official tasty-discover doc is said that it works over the executable that should be installed into the PATH.

[Anton-Latukha]

You were right.

It is my first, maybe second, passing-by/meating tasty-discover. Opened Report for them so they mention the setup.

[Anton-Latukha]

Store-remote test suite also requires Nix to be installed.

[Anton-Latukha]

Done.