Remove unnecessary test dependencies

[glefloch]

This branch leverage all dependencies used in gradle test IT. Addresses task number 2 from #15686.

@famod, let's see how build goes :). I manually updated the pom.xml.
In the pom.xml, there are some -deployment dependencies that are not used in any gradle project (like quarkus-grpc-deployment, quarkus-kotlin-deployment) should we keep them?

[famod]

I manually updated the pom.xml.

Don't trust my script? 😄

In the pom.xml, there are some -deployment dependencies that are not used in any gradle project (like quarkus-grpc-deployment, quarkus-kotlin-deployment) should we keep them?

If the runtime counterparts are used: yes absolutely! For the same reason we enrich all other ITs with those minimal deployment dependencies: To ensure Maven builds the respective deployment module(s) before the IT module.

[famod]

GH actions are broken ATM: https://www.githubstatus.com/incidents/s654n76c1bwr

[famod]

Ah this reminds me of something I wanted to ask you anyway: In CI we use .github/mvn-settings.xml for Maven, which uses the Google EU central mirror, but I have seen Gradle tests downloading stuff from central instead.
So I guess something is missing to pass it to Gradle in CI?

[glefloch]

Actually, I don't know, if this is a central mirror, I think this could be ok. I will add it too, in case of mavenCentral() failure, it will be used.

[famod]

I've just rebased this branch to trigger CI now that GH Actions are back to normal. I hope you don't mind. 🙂

[famod]

LGTM!

Not sure if anyone else should have a look before merging. I'll leave this up to you @glefloch.

[gsmet]

This is very useful, thanks for taking the time to do that!