I'll be reverting the PR to select/unselect datatables: #45313

I moved the code for changing the alertmanager_api_host, prometheus_api_host and grafana_api_url from the tests to the script to reduce the complexity of the tests. We are not actually testing anything there just making sure the environment is ready and the urls are okay. Because by default, these urls are set with fqdn and kcli env has issues with the fqdns.
Also by doing this it reduces some 404 errors coming from the node-exporter and prometheus so that the tests won't be affected by it.

In addition to this I reduced the count of node-exporter to 2 before starting the test. Its because, if we try to drain a host that has a node-exporter in it, that will cause a 404 error momentarily and that will cause the cypress to fail again. By positioning it into the script itself, this issue won't be there.

There used to appear an ExpressionChangedAfterChecked error in the service-daemon-list component because of the relativeDate pipe. And I did some searching and its a known issue with the date pipes . The good thing is that this will only happen in the developer environment. The easiest and proper way to catch this is to manually do the changeDetection which I done using a timeout.

There are some minor cleanups too where I do a proper cleanup by deleting the pool as well as the .kcli folder. Its to prevent errors like fedora36 image not found and it causes the vms to not start and that will make the test to hang there. The downside of doing this is that everytime the test needs to run in an environment it'll need to download the fedora36 image, but it'll make the test a bit more foolproof.

Fixes: https://tracker.ceph.com/issues/57511
Fixes: https://tracker.ceph.com/issues/57386
Signed-off-by: Nizamudeen A nia@redhat.com

Contribution Guidelines

• To sign and title your commits, please refer to Submitting Patches to Ceph.

• If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

Checklist

• Tracker (select at least one)
  • References tracker ticket
  • Very recent bug; references commit where it was introduced
  • New feature (ticket optional)
  • Doc update (no ticket needed)
  • Code cleanup (no ticket needed)
• Component impact
  • Affects Dashboard, opened tracker ticket
  • Affects Orchestrator, opened tracker ticket
  • No impact that needs to be tracked
• Documentation (select at least one)
  • Updates relevant documentation
  • No doc update is appropriate
• Tests (select at least one)
  • Includes unit test(s)
  • Includes integration test(s)
  • Includes bug reproducer
  • No tests