feat: Introduce Playwright for UI testing

Instead of using Robot Framework which does not run during a `mvn install`. Playwright seems to be the better approach. We can now write them as normal JUnit test and they are executed during a build.

Additionally this PR solves some interesting bugs found during writing Playwright tests:

- A reset of a lesson removes all assignments as a result another user wouldn't see any assignments
- If someone solves an assignment the assignment automatically got solved for a new user since the assignment included the `solved` flag which immediately got copied to new lesson progress.
- Introduction of assignment progress linking a assignment not directly to all users.

src/it/java/org/owasp/webgoat/integration/DeserializationIntegrationTest.java

@@ -0,0 +1,33 @@
+package org.owasp.webgoat.integration;
+
+import java.io.IOException;
+import java.util.HashMap;
+import java.util.Map;
+import org.dummy.insecure.framework.VulnerableTaskHolder;
+import org.junit.jupiter.api.Test;
+import org.owasp.webgoat.lessons.deserialization.SerializationHelper;
+
+public class DeserializationIntegrationTest extends IntegrationTest {
+
+  private static String OS = System.getProperty("os.name").toLowerCase();
+
+  @Test
+  public void runTests() throws IOException {
+    startLesson("InsecureDeserialization");
+
+    Map<String, Object> params = new HashMap<>();
+    params.clear();
+
+    if (OS.indexOf("win") > -1) {
+      params.put(
+          "token",
+          SerializationHelper.toString(new VulnerableTaskHolder("wait", "ping localhost -n 5")));
+    } else {
+      params.put(
+          "token", SerializationHelper.toString(new VulnerableTaskHolder("wait", "sleep 5")));
+    }
+    checkAssignment(url("InsecureDeserialization/task"), params, true);
+
+    checkResults("InsecureDeserialization");
+  }
+}