Playwright + Cucumber: Working version

[carlosthe19916]

No description provided.

[queria]

Hm seeing the e2e github check failing, it made me realize we want want to structure/tag/... the feature files in a way we can select subsets of which to execute:

• not all of tests may fit all envs/setups (e.g. may need longer execution time/resources, e.g. multiuser, need cves ingested etc)
• may be specific for only part/subset of ui (selective triggering on PRs?)

Not saying it would be needed right now, but maybe we could start with such set for what we want enabled in github checks.

[queria]

I think it could be good to also mention here the other modes of operation,
like which situation they can be used for please?

(e.g. the test:trace, test:host or any other useful tips for debug/devel)

[carlosthe19916]

Done, thanks

[carlosthe19916]

@vobratil @queria I changed the status of this PR to "Ready to be reviewed".
I will be out for the rest of week and I could not manage to be in contact with you guys, my apologies.

What I would suggest is to review this PR and if approved it can be merged. The feature implementations in this PR should be taken as a guidelines only because the final features will be the ones you all are defining in the other PRs.