Upgrade quarkus-arquillian to use JUnit 5

[Sgitario]

Fix #27812

[Sgitario]

If you decide to proceed with the changes in this pull request, it should be noted in the migration guide as a breaking change.

[gsmet]

@Sgitario if /we/ decide, you're part of the team.

[gsmet]

@mkouba did you remember why you targeted JUnit 4? Was it because of a lack of support of JUnit 5 in Arquillian or did we need it for some TCKs?

[Sgitario]

@mkouba did you remember why you targeted JUnit 4? Was it because of a lack of support of JUnit 5 in Arquillian or did we need it for some TCKs?

It seems that some TCKs need the support of JUnit 5. So, I've just updated the pull request to support both JUnit 5 and JUnit 4.

[mkouba]

@mkouba did you remember why you targeted JUnit 4? Was it because of a lack of support of JUnit 5 in Arquillian or did we need it for some TCKs?

It was the lack of support in Arquillian. And I believe that the TCKs that used JUnit at that time were using JUnit4 APIs.

[gsmet]

OK, I think we're not far from being able to merge this PR.

I added a few comments. As for testing JUnit 4, it's either simple and we do it or it's not and we can live without it. Don't spend time on that.

[Sgitario]

PR updated with the resolved change requests.

[gsmet]

Thanks. Nice having this ready for future MP versions.

[gsmet]

@radcortez FYI regarding MP TCKs.

[quarkus-bot]

Failing Jobs - Building d8d9cc7

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 MacOS M1	Set up runner	⚠️ Check →	Logs	Raw logs
✔️	JVM Tests - JDK 18