Add test suite in case of FIPS is enabled

[phracek]

It would be nice to test in upstream also ruby container in case of FIPS is enabled on host machine.

• First of all the GitHub Action should be present in the directory .github/workflows. The content should be similar like this https://github.com/sclorg/s2i-nodejs-container/blob/master/.github/workflows/container-fips-tests.yml
• The second one are alone tests.

1. In case of FIPS mode is disabled on host, then Ruby FIPS mode should not be executed at all or it should fail.
2. In case of FIPS mode is enabled on host, then detection if FIPS mode from ruby point of view has to passed.

The detection of FIPS mode is present in this file /proc/sys/crypto/fips_enabled.

It would be nice to have two test cases.

• check FIPS from ruby code like it is here: https://github.com/sclorg/s2i-nodejs-container/blob/master/test/test-lib-nodejs.sh#L485
• check FIPS from ruby application point of view.

A similar pull request in s2i-nodejs-container is here: github.com/sclorg/s2i-nodejs-container/pull/493, where you can take inspiration.

[jackorp]

#592 merged, tests pass. Ruby in container detects when FIPS is enabled and when disabled, and in the tests it checks that it is consistent with the host (IOW FIPS enabled host runs FIPS enabled Ruby container).

The app checks 2 ciphers and 2 hashes (see commit message), one of each is disallowed in FIPS and expected to fail the other are allowed in FIPS and are expected to pass. An exception is raised when an attempt is made to use the disallowed crypto. That exception is caught in FIPS and 200 OK is returned from the app as a response as we expect the disallowed crypto will fail if it would not fail, a non-OK code is returned and test assert fails.

If there are any other exceptions, it is not expected, the 500 HTTP error code is returned as it is not expected state.