fix: move to use junit+allure over karate

[maxandersen]

I love Karate and I'll always be a fan of it but
as time passed I realized it is a big dependency to have
with all the javascript/nashorn compabilitie for something
that for us is just calling out to a shell and does string comparisons.

This starts removing need for using Karate and instead uses plain
JUnit with assertj as gradle integration tests + using Allure to collect intermediate step results.

That last part was/is a key feature of karate where we can see all the steps
before and after a reported failure.

To run the build and see report try out just itestreport

end result is to remove karate/itests possibly even the asserta ones (they only run on non-windows anyways) and have it all handled in gradle run and standard junit execution and reporting.

[maxandersen]

this is related to #1967 but it is not required we move everything to assertj - can do it iteratively.

[maxandersen]

goal of this would eventually remove need for the various workarounds/managing of karate tests.

[maxandersen]

added fix to ensure actual built jbang is on path so it will succeed in github action

[quintesse]

That would be nice, because running the karate tests always messes up my system somewhat. Hopefully when running from JUnit we can set up a proper test environment.

[maxandersen]

Hmm - karate was supposed to run isolated - done the same setup now at least :)

[quintesse]

For me it always created a couple of files and modified one. I almost committed those changes by mistake a number of times.

[maxandersen]

ah yes - true; there is some of that - being inside proper java code should make it much easier to track down.