### Feature and motivation

Selenium still uses JUnit 4 (see eg https://github.com/SeleniumHQ/selenium/blob/702b3aae7385adf331d75cdeacd79720cf6b9c84/java/maven_deps.bzl#L56, https://github.com/SeleniumHQ/selenium/blob/702b3aae7385adf331d75cdeacd79720cf6b9c84/java/test/org/openqa/selenium/testing/JUnit4TestBase.java#L35)
JUnit 5 is out since 2017 and widely adopted.

I´m asking for this because there are issues when using JUnit 5 and Selenium 4 together. (https://github.com/SeleniumHQ/selenium/issues/9359) IMO such issues already should be recognized during automated testing.
@Ignore("it fails!")
  public void testGetSessionLogsWithLogCaptureDisabled() {
    PerSessionLogHandler handler = createPerSessionLogHandler();
    SessionId sessionId = new SessionId("session-1");
    handler.attachToCurrentThread(sessionId);
    LogRecord firstRecord = new LogRecord(Level.INFO, "First Log Record");
    handler.publish(firstRecord);
    SessionLogs sessionLogs = handler.getAllLogsForSession(sessionId);
    assertTrue(sessionLogs.getLogTypes().contains(LogType.SERVER),
      "Session logs for session should contain server logs");
    assertEquals(1, sessionLogs.getLogs(LogType.SERVER).getAll().size(),
      "Session logs for server should contain one entry");
    assertEquals(firstRecord.getMessage(),
      sessionLogs.getLogs(LogType.SERVER).getAll().get(0).getMessage(),
      "Session log should contain logged entry");
  }
  @Test
  public void testThreadToSessionMappingOnInitialNullSession()
    throws IOException {
    PerSessionLogHandler handler = createPerSessionLogHandler();
    LogRecord firstRecord = new LogRecord(Level.INFO, "First Log Record");
    LogRecord secondRecord = new LogRecord(Level.INFO, "Second Log Record");
    SessionId sessionId = new SessionId("session-1");
    handler.publish(firstRecord);
    handler.attachToCurrentThread(sessionId);
    handler.publish(secondRecord);
    assertMessagesLoggedForSessionId(handler, sessionId,
      "First Log Record", "Second Log Record");
  }
  @Test