ensure that var_sshd_set_keepalive is not set to 0 in rhel8 and rhel9 profiles

[vojtapolasek]

Description:

• modify all instances of var_sshd_set_keepalive variable so that it is not set to 0
• focus on rhel8 and rhel9 products, but in case it is common in a control file, modify rather the control file
• update profile stability tests

Rationale:

• context: after merging of Set the requires to sshd_set_keepalive on sshd_set_idle_timeout #11815 the rule sshd_set_keepalive starts being active in many profiles.
• that is fine, but the interpretation of the value "0" of this variable by sshd changed. In recent versions of ssh, if the value is set to "0", it disables the connection termination. That effectively goes against the reason why this configuration is used in hardening scenarios.

Review Hints:

• build rhel8 and rhel9 products
• check compiled profiles if there is not a case when var_sshd_set_keepalive is set to 0

[github-actions]

Start a new ephemeral environment with changes proposed in this pull request:

Fedora Environment

Oracle Linux 8 Environment

[github-actions]

🤖 A k8s content image for this PR is available at:
ghcr.io/complianceascode/k8scontent:11851
This image was built from commit: 474d405

Click here to see how to deploy it

If you alread have Compliance Operator deployed:
utils/build_ds_container.py -i ghcr.io/complianceascode/k8scontent:11851

Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and:
CONTENT_IMAGE=ghcr.io/complianceascode/k8scontent:11851 make deploy-local

[Mab879]

Please update the stable profile tests.

[codeclimate]

Code Climate has analyzed commit 474d405 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 59.2% (0.0% change).

View more on Code Climate.

[vojtapolasek]

fixed @Mab879