Development: Make compose for playwright tests more reliable

[muradium]

Checklist

General

• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Client

• I strictly followed the client coding and design guidelines.
• I documented the TypeScript code using JSDoc style.

Motivation and Context

Currently, the build plans for Playwright tests have inconsistent behavior and compose command sometimes fails due to having networks and network_mode both specified at the same time for artemis-playwright service. This happens because we override the networks using !reset [] action, but it is not an official compose syntax and sometimes the networks are not reset before the network_mode is used, which causes an error.

Description

This PR removes the networks section from playwright.yml compose file and leaves the networking to its extension. This change avoids the inconsistency caused by networks: !reset [] trick used on playwright-E2E-tests-mysql-localci.yml. Instead we specify only network-mode on it and we don't have to reset the networks as it's not specified on the parent compose file anymore.

Steps for Testing

• Code Review: Ensure that tests pass for valid reasons and improvements make sense.

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Code Review

• Code Review 1
• Code Review 2

[BBesrour]

code lgtm. However, there are many failing tests in the playwright jobs, is that normal?

[muradium]

@BBesrour I think that one failure happened due to another reason - probably because I started the tests too early while the push was still ongoing 😄 I'll run the build a few more times to make sure it's consistently succeeding

[SimonEntholzer]

Code, and all recent runs work reliably

https://bamboo.ase.in.tum.de/build/result/viewBuildResults.action?buildKey=ARTEMIS-AEPTMA1345-DA&buildNumber=21