Improve Develocity build scan support

[jprinet]

In order to improve the Develocity Build Scan support on the Log4j2 project, this PR provides:

• A PR comment and GitHub Workflow summary to ease navigation to the Build Scans
• Develocity short-lived tokens for authentication
• Build Scan publication only for build-reusable's Build step
• A rename from GE_ACCESS_TOKEN to DV_ACCESS_TOKEN

Note: A new input develocity-enabled is added instead of relying on the presence of the token to enable the Build Scan publication behavior. This allows to publish Build Scans when secrets are not available, following this approach.

Here is the summary that would be generated on the Log4j2's build workflow:

[jprinet]

Just a heads up @ppkarwasz that this PR will also add a comment to each submitted PR with the Build Scan summary table. I find it valuable but you may consider that a workflow summary is sufficient. If this is the case we can disable the PR comment with: add-pr-comment: false