Description of problem:
This is a follow-up from the bug #2029634 and #2029634, which implements the FIPS mode detection, but it is not correct because of two reasons:

 * any RHEL/Fedora configuration is detected as in FIPS mode
 * the templates are not modified to exclude the fips hostkeys (only the meta/10_top.j2 was modified, but the templates were not regenerated)

The result is that regardless the FIPS mode status, the ed25519 hostkeys
are not generated and checked:
```
TASK [ansible-sshd : Make sure hostkeys are available] **************************************************************
ok: [localhost] => (item=/etc/ssh/ssh_host_rsa_key) => {...}
ok: [localhost] => (item=/etc/ssh/ssh_host_ecdsa_key) => {...}
```
but they are included in the configuration file:
```
[root@5c5bfece6a22 tests]# cat /etc/ssh/sshd_config
[...]
HostKey /etc/ssh/ssh_host_ed25519_key
```

This is handled on non-fips systems by the systemd service which probably generates the keys and sshd stars ok in real systems (I tested only in containers so far). On FIPS systems, it might fail to start the service.

Version-Release number of selected component (if applicable):
rhel-system-roles-1.11.0-1.el8
rhel-system-roles-1.11.0-1.el9

How reproducible:
always

Steps to Reproduce:
1. set system into fips mode on RHEL8
2. run sshd role with default parameters

Actual results:
 * the ed25519 key is listed in configuration file in FIPS mode
 * the ed25519 key is NOT checked/created by the role out of FIPS mode

Expected results:
 * the ed25519 key is NOT listed in configuration file in FIPS mode
 * the ed25519 key is checked/created by the role out of FIPS mode


Additional info:
on RHEL9, this will not demonstrate as there are no default hostkeys in configuration file as the drop-in directory is used.