[JENKINS-70822] Improve plugin manager search

[timja]

See JENKINS-70822.

Consider multiple words rather than just doing sub string match

build token can now match build-token-root
Pipeline Groovy, can now match Pipeline: Groovy.

I had to implement a basic ranking algorithm in order for this to be usable as without it they appeared in the middle somewhere or even not in first 50 in some cases.

I restricted the multiple word search to just name and title as a lot of these words show up in the description.

Open to feedback :)

Testing done

Unit tests + searches in the UI especially the searches from the Jira ticket

Proposed changelog entries

• JENKINS-70822, Plugin manager search is improved

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

@mention

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]

Thanks for taking care of this!

First quick test has an unexpected result when searching for workflow cps though, with Pipeline: Groovy (and really any relevant plugin) way down:

Similarly, pipeline cps has several Pipeline-related results first, before showing Pipeline: Groovy. Is the weight given to matching all tokens perhaps too low? (Or perhaps even only show results not matching all terms if there is no hit for all terms?)

[BobDu]

Looks this PR will has conflict with #9162

Can we first merge #9162 into master, and then update this PR branch use master.
Because #9162 it's just a simple fix to restore the behavior before the code was refactored.

[github-actions]

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

[A1exKH]

Please, resolve merge conflicts for this PR.