chore(test): added tests for multiple lxd server versions [WD-8616]

[mas-who]

Done

• Adjusted CI to run e2e tests against multiple lxd server versions
• Added tests for lxd v5.0/stable
• Adjusted existing tests with features that does not exist in lxd v5.0/stable to be skipped
• Added test fixture to annotate tests with lxd version

QA

1. Run the LXD-UI:
   • On the demo server via the link posted by @webteam-app below. This is only available for PRs created by collaborators of the repo. Ask @lorumic or @edlerd for access.
   • With a local copy of this branch, run as described here.
2. Perform the following QA steps:
   • ensure CI passes
   • check that the output playwright report looks fine

[webteam-app]

Demo starting at https://lxd-ui-653.demos.haus

[edlerd]

As just discussed in person: Let's combine the browser and lxd-backend verison as project, that is communicated to playwright. This way we can avoid passing the LXD_VERSION as environment variable and get it on the playwright report on top level.

[edlerd]

QA from the report looks good. One question for a possible simplification below.

[edlerd]

Nice additions here 👍

[edlerd]

I am confused as the value passed here seems to be hardcoded. Is the actual value coming from the use block in playwright config? Maybe we don't need the value here, then?

Though, please keep this lxd-test file, because I am going to need it for the coverage very soon -- even if it turns out to be empty and just passes the base test at this point.

[mas-who]

The value set here is the default for the project use parameter. I referenced the playwright docs for parameterising projects. I think { option: true } is necessary but not sure if we can pass in a empty value for the first parameter of the array. Although passing in an empty value will look strange as well I rate, wdyt?

[edlerd]

If we need this definition here, I think keeping latest-edge as a default is reasonable.

Maybe we should document the test setup, as it lately became a bit more complex. Could you add a future story to extend the architecture file?

[mas-who]

will do, I did add a bit of context in the HACKING.md, but I think adding to the architecture file is also necessary. Will create a task for it 👍

[edlerd]

LGTM, I like the solution :)