[JENKINS-37241] Support for query parameters in autocomplete

[timja]

See JENKINS-37241.

Testing done

Verified that existing usages in core are unaffected:

1. Creating a logger and having logger names suggested. This one is a good test as it doesn't have a descriptor behind it as well.
2. Copy from in a new job

Created a change in Azure VM agents jenkinsci/azure-vm-agents-plugin#580 which uses the depends on functionality to access query parameters

Proposed changelog entries

• Developer: Add support for @QueryParameter to the autocomplete component
• Change autocomplete component to use POST for sending requests

Proposed upgrade guidelines

N/A

Submitter checklist

Beta 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

Beta 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).

[timja]

I thought about whether this should be a different attribute name, e.g. autocompleteFillDependsOn but I couldn't see when they would ever clash so I just left it as the same name

[timja]

copied from hudson-behaviour.js for the doCheck functionality.

It uses query string by default and then if the method is post it converts to parameters, (which is the default)

I didn't see any reason for there to need to be an option for get, I'm not aware of it ever being used for the doChecks

[Kevin-CB]

Sorry for the delay! I’ll get started on the security review now.

[janfaracik]

Tested locally and LGTM. Seems there's quite a few competing components for this in Design Library, would be good for us to recommend one of them (and maybe dissuade usage of the others if they're not as functional).