ci(refactor): extract build setup logic into setup-build

[tueda]

This patch extracts the build setup logic into a composite action called setup-build to avoid repeating similar steps in different jobs. The setup process includes installing dependencies and libraries, extracting tarballs, running autoreconf, and executing configure.

In the future, if we need to elaborate further on setting up libraries (including building and caching), such as MPI or FLINT, we can manage them all in one place.

There are several ways to organize shared logic in GitHub Actions:

• Script files: Hard to track in the GitHub Actions UI because everything appears as a single step when running a script file.
• Reusable workflows: Can't set environment variables for the caller. (setup-build needs to modify $LIBRARY_PATH etc.)
• Composite actions: Allow environment variable modifications, but do not show individual steps clearly in the UI. actionlint doesn't work for composite actions.

This patch adopts the last option. To mitigate the drawback, I added lines like ### Initialize setup ### in the run: field, which will appear in the logs.

[tueda]

Changed from tr ' ' '|no' to sed 's/ /|no/g' (I misunderstood how tr works).

[coveralls]

coverage: 49.241% (-0.004%) from 49.245%
when pulling a908805 on tueda:ci-setup-build-action
into e1289ac on vermaseren:master.

[tueda]

Rebased. Added features: zstd, mpich, openmpi. The default MPI is now openmpi. Also addressed the issue described in awalsh128/cache-apt-pkgs-action#150.

[tueda]

Updated.

[jodavies]

This looks to be building and caching flint also on Ubuntu, right? Then #703 will go in easily?

The actions setup looks much cleaner with this!

[tueda]

Yes, the action now builds FLINT 3.3.1 also on Ubuntu.

It also contains some untested features like ginac. The code in #640 is also partially included (but not tested).

[coveralls]

coverage: 54.37% (+0.7%) from 53.699%
when pulling ada1f0a on tueda:ci-setup-build-action
into e3eeea3 on form-dev:master.

[tueda]

Once this commit is included in a release, we can simplify the reference to v1.

[tueda]

I'm thinking about letting this action optionally run the build step (despite the name setup-build). In that case, the builds in test.yml (which are all common) can be removed by enabling a build feature flag.

[jodavies]

Right, this would speed things up (a bit) if the binaries are cached. At some point it might be worth taking a look at the slowest of the tests under valgrind, and trying to make an easier test which hits the same bug, if we would like the CI to run faster (since in the future, we would like to add a lot more tests for better coverage).

[tueda]

I just meant removing the five run: make -C sources -j 4 ${{ matrix.bin }} lines :-)
Caching the binaries would be tricky, but potentially useful.

[jodavies]

Then I misunderstood. In the context of your changes here it does make sense to remove as much duplicate build code as you can from the various test jobs indeed.

[tueda]

FLINT is now statically linked on macOS.

I also committed workflow improvements with more robust checks, and excluded extern/zstd and lib/flint from coverage.