[JENKINS-68404] Add script listener to track usage

[meiswjn]

This PR relates to jenkinsci/jenkins#6539 and https://issues.jenkins.io/browse/JENKINS-68404. It serves the purpose to track potentially dangerous usages of groovy scripts.
The script listener is called when a script is considered to be allowed to use. This also means that scripts running in a sandbox are not logged.

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[meiswjn]

@daniel-beck jenkinsci/jenkins#6539 (comment)

Let me know what you think.

[meiswjn]

Extends listener introduced in jenkinsci/jenkins#6539

[daniel-beck]

#configuring might be a good alternative to #using because that can determine who the user actually submitting the script is. It also has ApprovalContext which would probably remove the need for the API change.

[daniel-beck]

A basic pipeline:

Script: 'echo "hello world"' from origin: 'N/A' by user: 'null'

Once we've finalized the API here, looks like this needs a downstream change in workflow-cps or so.

[daniel-beck]

Looks like this PR needs to be re-filed from an origin branch, or from the fork of a committer (e.g. me), to pick up the changes to the Jenkinsfile, so we have an incremental build of this.

[lemeurherve]

@daniel-beck I've replayed it with the updated Jenkinsfile.

[daniel-beck]

@daniel-beck I've replayed it with the updated Jenkinsfile.

Cheater! (Thanks 😄)

[meiswjn]

With jenkinsci/jenkins#7056 being merged, I will continue on this PR soon :)