### 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.
SessionId sessionIdOne = new SessionId("session-one");
    SessionId sessionIdTwo = new SessionId("session-two");
    
    handler.attachToCurrentThread(sessionIdOne);
    handler.publish(firstSessionLog);
    handler.detachFromCurrentThread();
    
    handler.attachToCurrentThread(sessionIdTwo);
    handler.publish(secondSessionLog);
    handler.detachFromCurrentThread();
    assertMessagesLoggedForSessionId(handler, sessionIdOne,
      "First Session Related Log Record");
    assertMessagesLoggedForSessionId(handler, sessionIdTwo,
      "Second Session Related Log Record");
  }
  @Test
  public void testShouldReturnEmptyLogIfNoRecordHasBeenLogged()
    throws IOException {
    PerSessionLogHandler handler = createPerSessionLogHandler();
    assertNoMessageLoggedForSessionId(handler, new SessionId("session"));
  }
  @Test
  public void testShouldNotCopyThreadTempLogsToSessionLogsIfNoLogRecordForThreadPresent()
    throws IOException {
    PerSessionLogHandler handler = createPerSessionLogHandler();
    SessionId sessionId = new SessionId("session");
    handler.transferThreadTempLogsToSessionLogs(sessionId);
    assertNoMessageLoggedForSessionId(handler, sessionId);
  }
  private void assertMessagesLoggedForSessionId(PerSessionLogHandler handler,