Detect missing dependencies

Citing @jamesnetherton from https://github.com/apache/camel-quarkus/pull/1543

> I noticed that quarkus-resteasy transitively pulls in quarkus-netty. And since almost every itest uses resteasy, I was curious whether any extensions were getting their quarkus-netty deps for 'free'. Turns out the only problem was with olingo4.

In more general terms, it can happen that our extensions are missing explicit dependency on some Quarkus extension that happens to be pulled by quarkus-resteasy while our itests are still passing because resteasy happens to bring what's needed. A real world application not depending on resteasy may have issues.

Perhaps we should have a tool able to detect such missing dependencies.

Start by reading the cited pull request 1543 and the olingo4 integration tests to understand how quarkus-resteasy currently supplies quarkus-netty transitively. The issue is done when a defined tool can identify extensions missing explicit Quarkus dependencies despite passing integration tests.

Written by the indexing model from the issue text.