Integration tests (libssh, httpd, bind)

[The-Mule]

This PR adds two new tests (for httpd and bind) and re-factors previously added test for libssh. Tests are intended to run in CI (github actions) but they can be executed on any Fedora (39 and newer) as follows (GIT_URL defaults to this repository and GIT_REF to the main branch):

# cd tests/integration
# GIT_URL=https://github.com/The-Mule/pkcs11-provider.git GIT_REF=integration-tests bash -e libssh.sh

Testing requires bash -e option. Non-zero exit code means failure. Provider debug logs are always printed out at the end (regardless of the result). All three tests uses softhsm token (bind test does so via p11-kit server proxy). Please notice that until Fedora 40 is released both httpd and bind test need to use a specific docker image.

[The-Mule]

New integration tests results can be found in the checks too (all passes).

[simo5]

Mostly LGTM, but I am afarid of the time it may take to run this is there are a lot of steps that pull lots of data from the network.

[simo5]

So the integration step took 6 minutes.
4.42 minutes were spent in downloading/installing stuff.
We should probably use caches aggressively.

See this for inspiration:
https://github.com/latchset/kryoptic/blob/15bd875f6ce5acbaa93c909074f1da2812215a68/.github/workflows/build.yml#L27

[The-Mule]

I'll take a look how to make it faster, a lot of time is spent on installing F40 packages now. But maybe that can be cached too somehow.

[simo5]

I'll take a look how to make it faster, a lot of time is spent on installing F40 packages now. But maybe that can be cached too somehow.

Se previous comment, you just need to copy that code :-)

[The-Mule]

With matrix strategy integration tests workflow only takes ~2 minutes (1:57) now. I tried to add actions/cache on top of that but it had no effect in this case (it looks like dnf step is now running at the same time in all three jobs).

[simo5]

Awesome thanks,
I think we should still cache because some tests are still dominated by install time, and it is all in download time. But we can do that in a followup PR.