### 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.
public void testThreadToSessionMappingOnTwoInitialNullSessions()
    throws IOException {
    PerSessionLogHandler handler = createPerSessionLogHandler();
    LogRecord firstRecord = new LogRecord(Level.INFO, "First Log Record");
    LogRecord secondRecord = new LogRecord(Level.INFO, "Second Log Record");
    LogRecord anotherRecord = new LogRecord(Level.INFO,
      "Another Log Record");
    LogRecord oneMoreRecord = new LogRecord(Level.INFO,
      "One More Log Record");
    SessionId sessionIdOne = new SessionId("session-1");
    SessionId sessionIdTwo = new SessionId("session-2");
    handler.publish(firstRecord);
    handler.attachToCurrentThread(sessionIdOne);
    handler.publish(secondRecord);
    handler.detachFromCurrentThread();
    handler.publish(anotherRecord);
    handler.attachToCurrentThread(sessionIdTwo);
    handler.publish(oneMoreRecord);
    assertMessagesLoggedForSessionId(handler, sessionIdOne,
      firstRecord.getMessage(), "Second Log Record");
    assertMessagesLoggedForSessionId(handler, sessionIdTwo,
      "Another Log Record", "One More Log Record");
  }
  @Test
  public void testThreadToSessionMappingAndClearMapping() throws IOException {
    PerSessionLogHandler handler = createPerSessionLogHandler();
    LogRecord firstSessionLog = new LogRecord(Level.INFO,
      "First Session Related Log Record");
    LogRecord secondSessionLog = new LogRecord(Level.INFO,
      "Second Session Related Log Record");