So that it can be called from the container-tools module without
duplication. For technical reasons this requires calling the test entry
script from a different directory, so parameterize it.
Rename the test from "browser" to "cockpit-podman" so that it is
more descriptive within a module test.
Drop the TEST_OS hack, tests of current version recognizes RHEL 8.3 just
fine (and in fact depends on it).
Related: rhbz#1821193
Re-use the test skeleton from cockpit. Just run a single integration
test for now, until we make them properly @nondestructive upstream [1].
Run chromium and the test directly on the test bed. For cockpit-podman
tests it's not practical to run them in a cockpit/tasks podman
container, as that container interferes too much with the tests.
[1] https://github.com/cockpit-project/cockpit-podman/pull/356
