Ban and remove quarkus logger in our own source

[holly-cummins]

See discussion here: #48432 (comment)

In order to make the ban work, I explicitly list every logger method, so that Log itself didn't trigger the ban. An alternative would be to had to exclude Logger itself from forbidden api checking, either with a maven exclude or @SuppressForbidden annotation. That reduces the risk of missing one method from my list, but increases the risk of missing something else banned in Log.

While getting CI green I spotted three classes which were using Log. Only one of them was my fault, as far as I can tell. :)

In case we want it later, this is what we maven exclude looks like:

                                <!-- We want to exclude Log from the check for Log or the checker goes mad, which means we have to exclude it from all checks -->
                                <excludes>
                                    <exclude>io/quarkus/logging/Log.class</exclude>
                                </excludes>

[gsmet]

I think this is good and we should merge it but I would like to have #48655 in first as atm ForbiddenAPIs is run on a small subpart of the tree so there might be more changes needed here once we generalize it.

I also think once my PR is in, we should start aggressively ban everything that shouldn't be used in our tree.

[gsmet]

I rebased on top of my PR and this should be all good now.

It spotted several more occurrences so it was worth applying the plugin to the whole codebase.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 67e525c.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.