Update airbase to 148

[wendigo]

Fixes incorrect junit/surefire integration that isn't working with the latest surefire plugin.

junit-jupiter-engine should be a module dependency, rather then surefire plugin dependency.

[martint]

In these examples, it shows up as a plug-in dependency: https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-platform.html#api-engine-versions-segregation

[wendigo]

@martint but it doesn't work anymore :( We had it mixed anyway. Some modules were following method in this PR, some were adding engine to the surefire deps. Now it seems to work properly and all transitive dependencies that are needed are resolved (this wasn't the case when the jupiter-engine was in the surefire deps).

[wendigo]

@martint PTAL

[martint]

But do we know why it starts failing with the surefire plugin upgrade? That seems like a regression in the plugin, and would suggest we shouldn't update until that bug is fixed.

[wendigo]

@martint I guess that this is related to apache/maven-surefire#617. Anyway I personally think that current behaviour is the correct one. Not the previous one

[wendigo]

@martint I'd like to move forward with this change as it contains some needed dependency upgrades.

[wendigo]

Ping @martint

[martint]

Anyway I personally think that current behaviour is the correct one. Not the previous one

How so? It would be preferable to be able to specify the dependencies in the plugin spec so that they could potentially be applied to the whole project eventually by configuring it in the root pom instead.

I'm fine with doing this for now if necessary to update the other dependencies you mentioned, but as soon as the underlying bug in surefire is fixed, we should change it back.

[wendigo]

@martint i'm ok with that