follow up for playwright docker container and script test-e2e

What does this MR do?

• playwright container now works in dev and test environment
• can be called via ./scripts/test-e2e test (for test) or ./scripts/test-e2e (for dev).
• ./scripts/test starts test-e2e as 1st test.

How confident are you it won't break things if deployed?

Links to related issues

https://yunity.slack.com/archives/C1T1ZM9A4/p1703154354195909

How to test

Screenshots (if applicable)

Checklist

• added a test, or explain why one is not needed/possible...
• no unrelated changes
• asked someone for a code review
• set a "for:" label to indicate who will be affected by this change
• added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
• added an entry to CHANGELOG.md
• added a short text in the release notes to /release-notes/YYYY-MM.md
• Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/region?bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
  • Consider writing a detailed description in German.
  • Describe in a few sentences, what should be tested from a user perspective.
  • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
  • Be aware, that also non technical people should understand.