Improve documentation on the usage of io.quarkus.logging.Log in extensions

[SergioRuyDev]

Description:

The current Quarkus documentation suggests using Log only in application classes, not in external dependencies. However, Log can work in extension modules if they have a Jandex index, although this behavior might not be reliable.

The documentation doesn’t mention that:

The stack walk fallback in logging can cause performance issues. Extensions should use standard loggers like Logger.getLogger() instead of Log.

[github-actions[bot]]

🙈 The PR is closed and the preview is expired.

[quarkus-bot[bot]]

---

:waning_crescent_moon: This workflow status is outdated as a new workflow run has been triggered.

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 10adfc9520937f95f7d2b38c6497a94376e4c44f.

:white_check_mark: 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.

[quarkus-bot[bot]]

---

:waning_crescent_moon: This workflow status is outdated as a new workflow run has been triggered.

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 40c48a405909875585c4a36909e556927a4e03f2.

:white_check_mark: 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.

[quarkus-bot[bot]]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 2656790f62e209e1337134fed70b2d7e9aa3a1db.

:white_check_mark: 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.