Add experimental 'Parameters' detail for runs

[janfaracik]

This PR adds a quick way to view Parameters for a run for the experimental run page.

The intention behind this is to:

• Reduce items in the sidepanel
• Keep details of a run together
• Avoid disrupting the user's context by opening the dialog on the same page
• Improve performance by avoiding a full page reload
• Make it easy to copy past parameters

This PR also adds a <l:dialog /> component, making it easy for developers to display dialogs with deferred loading of their contents, built on top of the existing renderOnDemand.

Testing done

• Button hides for non-parameterised runs
• Button appears for parameterised runs

Proposed changelog entries

• Add experimental 'Parameters' dialog for builds

Proposed changelog category

/label web-ui,rfe

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@jenkinsci/sig-ux

Before the changes are marked as ready-for-merge:

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[timja]

Not tested this yet, is there a way to send a link that will have the parameters dialog open?
I imagine that's a relatively common use-case, to send a link to someone with the parameters for a build?

e.g. maybe a URL fragment #parameters that will auto open the dialog and clicking the link appends it.

[janfaracik]

Good idea - I've updated it so that the hash is set when opening, navigating to that url then opens the dialog.

[timja]

LGTM!

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!