The Ansible Tasks in this rule manipulate with many unrelated files such
as /etc/sestatus.conf or /etc/krb5.conf.  The reason is that they
wrongly use the chrony_conf_path variable. They get the name of the
parent directory and look for all .conf files there. This probably works
nicely for Ubuntu products, where chrony_conf_path is set to
/etc/chrony/chrony.conf, but creates harm in all other products where
chrony_conf_path is set to /etc/chrony.conf, so the dirname is /etc and
the search matches all *.conf files in /etc.

We will fix this problem by explicit using the chrony_d_path content
variable which defines path to the chrony configuration directory.

Adds scenarios testing the configuration in the .d directory.

- consistent support for the configuration directory
- always use product properties `chrony_conf_path` and `chrony_d_path`
  for the configuration file and configuration directory instead of
  using hard-coded path
- do not pass if no server is set, this align the behavior with RHEL
  and Ubuntu STIGs

Use the "variables" keyword in the test scenario headers instead of the
"profiles" keyword. These test scenarios aren't a regression test
special to STIG. The profile was set in order to set the XCCDF Value
value. This is legacy usage of the "profiles" keyword and we recommend
using "variables" for this situation.