Make sure *no* countme flag is present.

Also adapt the HTTP matching patterns in the countme feature file
accordingly.

This will be used in the next commit, no functional change right now.

Shuffle some steps around, add blank lines and also emphasize that we're
dealing with *calendar* weeks/months (i.e. aligned with the calendar,
not with the first countme hit).

No functional change.

We'll need this step in a "when" context in the next commit.

No functional change.

Adapt the countme feature to the libdnf fix for issue #1611, namely:

- Turn the main scenario into a scenario outline to capture the various
  machine-id(5) configurations (see the table).

- Add an upgrade scenario (from F39 to F40) that verifies that system
  age is now independent of $releasever on systems with a machine-id
  file.

- Use NO_FAKE_STAT=1 in faketime invocations so that filesystem
  timestamps are *not* reported relative to the target time (this would
  break our custom machine-id timestamps we set here), see faketime(1)
  for details.

- Add a new MachineId class to encapsulate the machine-id file, similar
  to OSRelease.

- Mark the touched scenarios as destructive (due to them overriding the
  machine-id file).

There is a difference between `makecache` command from dnf5 and old
dnf4. dnf4 always fetches new metalink/mirrorlist and ignores expiration
of the repo, this is likely a long-standing bug. On the other hand dnf5
doesn't contant the remote if the cache is fresh.

Since the countme tests rely on the dnf4 behavior ensure it by using
`--refresh` for dnf5.

According to OS-RELEASE(5) man page values with characters outside of
A–Z, a–z, 0–9 such as spaces or dots must be enclosed in double/single
quotes.

While handling of the `os-release` file is still work in progress in
dnf5 make the step more robust by wrapping all values in quotes.

Old dnf4 was able to handle even non-conforming `os-release` file.