Decide what to do with OVAL generation tests

Currently, the OVAL generation tests [added here](https://github.com/AlmaLinux/albs-web-server/pull/1100) were disabled later on in the `preflight` workflow due to [this problem](https://github.com/AlmaLinux/build-system/issues/429) and as part of [this PR](https://github.com/AlmaLinux/albs-web-server/pull/1112).

Ideally, `preflight` should also be able to perform such tests, as we won't notice if something got broken until the commit lands master.

There are 3 options:
* We keep it as it is - and we know that we should always keep an eye on oval tests after anything is merged
* We try to also run the tests, despite of the limitations to pull the code from the private repo when running the `preflight` workflow
* We move the tests out of web_server and re-imagine these tests somewhere else (in the private repo, or in some intermediate one)