Bump sbt-jupiter-interface to 0.13.x

[lihaoyi]

Copy of #3501 opened from a separate repo to avoid double testing

Seems like the issue is that the jupiter-test-interface is not configured correctly and is thus missing the test class name as part of the success error reporting

./mill -w 'example.javalib.testing[3-integration-suite].local.test'

[2951]   Test run started (JUnit Jupiter)
[2951]   Test run started (JUnit Jupiter)
[2951]   Test #helloworld() started
[2951]   Test #hello() started
[2951]   Test #helloworld() finished, took 0.014s
[2951]   Test #hello() finished, took 0.013s
[2951]   Test #world() started
[2951]   Test  finished, took 0.025s
[2951]   Test #world() finished, took 0.0s
[2951]   Test  finished, took 0.025s
[2951]   Test  finished, took 0.038s
[2951]   Test run finished: 0 failed, 0 ignored, 1 total, 0.05s
[2951]   Test  finished, took 0.037s
[2951]   Test run finished: 0 failed, 0 ignored, 2 total, 0.049s

[lihaoyi]

@jodersky could you help investigate this one? It might be related to #3983; probably not caused by it, but in the same area of the codebase around the jupiter test framework

[jodersky]

I narrowed the change in behavior down to this commit sbt/sbt-jupiter-interface@d9537f9 in sbt-jupyter-interface. Looking into it

[jodersky]

Even more precisely: sbt/sbt-jupiter-interface@7adbdd0

[jodersky]

Upstream issue sbt/sbt-jupiter-interface#125 (comment)

[jodersky]

FYI, I've submitted a fix uptream awaiting approval

[lihaoyi]

@jodersky looks like sbt-jupiter-interface 0.13.2 is out, so we may be able to make progress on this