Validate Logstash pipeline ID when creating.

[mashhurs]

Description

This PR change validates Logstash pipeline ID when creating a pipeline with _logstash/pipeline/{ID}. The ID must start with letter or underscore and can contain only letters, underscores, dashes, hyphens and numbers.

It is due to consistency across the stack:

• Logstash references states that pipeline ID must "begin with a letter or underscore and contain only letters, underscores, dashes, and numbers". However, when calling ES API through Kib Dev console, it still creates the pipelines. This PR addresses this issue.

• Kibana mentions this in the docs, it does validate on frontend. One gap I found was Kibana API wasn't also validating pipeline ID. So, I have opened a PR to close this gap: Validates Logstash pipeline ID in Kibana API level. kibana#236347

• Closes Logstash Pipeline API should enforce pipeline name restrictions #134301

How to test?

• pull this change
• run with Kibana if you would like, guide is here. See the following screenshot which I tested locally to check user experience.
• alternatively, run elasticsearch after compile: the fastest way is to create local distro ./gradlew localDistro and run the artifact created under "build/distributions" path.
• call /_logstash/pipeline/{pipelineID} API

curl --location --request PUT 'https://127.0.0.1:9200/_logstash/pipeline/1main' \
        --header 'Authorization: ••••••' \
        --data ''
      {
          "error": {
              "root_cause": [
                  {
                      "type": "illegal_argument_exception",
                      "reason": "invalid pipeline id [1main]: must begin with a letter or underscore, can contain only letters, underscores, dashes, and numbers"
                  }
              ],
              "type": "illegal_argument_exception",
              "reason": "invalid pipeline id [1main]: must begin with a letter or underscore, can contain only letters, underscores, dashes, and numbers"
          },
          "status": 400
      }

Template

• Have you signed the contributor license agreement? - Y
• Have you followed the contributor guidelines? - Y
• If submitting code, have you built your formula locally prior to submission with gradle check?
  • ./gradlew check succeeded
• If submitting code, is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
• If submitting code, have you checked that your submission is for an OS and architecture that we support?
• If you are submitting this code for a class then read our policy for that.

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)