### Description

Logstash uses the endpoint  `_logstash/pipeline` to retrieve the pipelines configuration from Central Management.
Logstash permit to use the `*` wildcard operator to specify the pipeline names, so a user is not required to list all the pipelines, but just capture the common not changing part of the name. 
Suppose the user has a pipelines with common prefix (for example `pipeline_proxy_1`..`pipeline_proxy_10`), he could also add `pipeline_11` without restarting Logstash and changing the option `xpack.management.pipeline.id`.

Actually the feature is implemented on Logstash side, retrieving all the pipelines and then filtering out the ones that doesn't match; this is a waste. 
This feature request asks to implement the wildcard operator selector on Elasticsearch side.

The rules for wildcard in pipeline names are:
must begin with a letter or underscore and contain only letters, underscores, dashes, and numbers wildcard character `*` is also acceptable and follows globbing rules.

The regexp is defined [here](https://github.com/elastic/logstash/blob/0887d7609df9ba72a5d0cd003c639b16da198622/x-pack/lib/config_management/bootstrap_check.rb#L17-L19).

We could imagine to use the `_logstash/pipeline/<pipeline_id>` where the pipeline_id is a list of comma-separated id (like it's today) but permitting the pipeline_id to use the wildcard operator.

Related:
- Logstash ER https://github.com/elastic/logstash/issues/13868



x-pack/plugin/logstash/src/test/java/org/elasticsearch/xpack/logstash/action/TransportGetPipelineActionTests.java
/*
 * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
 * or more contributor license agreements. Licensed under the Elastic License
 * 2.0; you may not use this file except in compliance with the Elastic License
 * 2.0.
 */
package org.elasticsearch.xpack.logstash.action;
import org.apache.logging.log4j.Level;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
import org.elasticsearch.action.ActionListener;
import org.elasticsearch.action.ActionRequest;
import org.elasticsearch.action.ActionResponse;
import org.elasticsearch.action.ActionType;
import org.elasticsearch.action.get.GetResponse;
import org.elasticsearch.action.get.MultiGetItemResponse;
import org.elasticsearch.action.get.MultiGetResponse;