[skip-ci] Make leak-detection readable by humans

[cevich]

Previously when a leak was detected under any circumstance, the workflow would splat out a giant wall of gray, unreadable git-log text. This often enormous text might contain, somewhere, possibly, maybe, a little tiny snippet of code that leaks a secret.

Improve the situation greatly by providing easy-to-use URLs that covers the relevant changes based on the triggering context (new pr, force-push, or merge). Store the former (often) giant git-log output into a file and stuff it into the artifacts in case it's ever useful.

Does this PR introduce a user-facing change?

None

[cevich]

The intended output urls should look something like what I've linked below for "shows url" against this reference PR. I've also linked the exact "workflow" for each event.

Example URLs shown in workflow log:

• New PR workflow - shows url
• A force-push workflow - shows url
• A PR merge workflow - shows url

Note: I made this list by manually copy-pasting based on what the code changes should echo. I can't easily test the actual workflow changes before they're merged. If it doesn't work, I'll open up followup PRs to correct.

Edit: If it helps, in each "workflow" link, there's a Show important context details log item with a The trigger event JSON drop-down. That shows where the SHA's are being queried from.

[cevich]

@edsantiago @lsm5 not super-critical, but when you get a chance PTAL. I'm hoping this should ease the pain of checking for leaks based on a flood of podman-monitor e-mails.

This doesn't make the leak-review task completely effortless, but at least it colorizes the diff in green and red, and offers a 'hide' button for each file in the commit 😄

[mheon]

LGTM

[rhatdan]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cevich, rhatdan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rhatdan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[TomSweeneyRedHat]

LGTM