Add grouping to Command Palette

[janfaracik]

This PR adds grouping to the Command Palette, making it easier to identify what each result is.

There are a range of prebuilt groups, UnclassifiedSearchGroup, ItemSearchGroup, ComputerSearchGroup, ViewSearchGroup, and UserSearchGroup. Developers can add custom groups too, for example, Design Library could add a group for its components and patterns.

Groups by default don't have a specific ordering, however, the items group is configured to always appear first, and the unclassified group is configured to always appear last. Results are then ordered by name.

I've also done some minor tidy up to the interface, making the overlay a little less invasive.

Testing done

• Groups appear as expected

Proposed changelog entries

• Add grouping to Command Palette

Proposed upgrade guidelines

N/A

Submitter checklist

Preview Give feedback

1. The Jira issue, if it exists, is well-described.
2. 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.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. 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).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. 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

Preview Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. 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).
6. 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).

[daniel-beck]

Any thoughts on renaming "Jobs" to just be "Items" so we can include folders too? They're part of the same list when in a view, so I think it'd make sense to group them when searching too.

If all items are intended to appear there, then it should be "Items". If you only want things representing "projects" there, then regular folders would not be, and in a separate section of "other items".

I'm not sure what is the better approach. Having all items there certainly would be simpler (no need to think too hard about what kind of thing in this categorization a multibranch pipeline is…), plus they're currently displayed in the same sort of list as well. So I tentatively prefer this one. This could always be split up later if we don't like it long-term, while merging seems more complicated.

Another option might be to (re)use the item type categories that are currently hidden from view (supposed to be temporary in 2016…). Go to "New Item" page and remove the class flat from div#items (also, yay, UI labels with "Projects" 🤦 ). These could be used either as top-level groups in this group scheme, or as nested subgroups within the "Items" top-level category.

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[janfaracik]

Great. I've renamed Projects Jobs to Items - like you said it should keep categorisation simpler. If the need arises in the future to split them out then we can do that then.

[scherler]

https://issues.jenkins.io/browse/JENKINS-75312?focusedId=452592&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-452592 Maybe one link or using a form and the submit will lead to the search page again (aka not selecting the first match) could be part of the PR? I am ATM looking into fixing the problem that I mentioned https://issues.jenkins.io/browse/JENKINS-75294?focusedId=452602&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-452602 and stumbled on the other ticket

[timja]

LGTM

[krisstern]

/label ready-for-merge

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