Add support for inputs with qualified names

[jsoriano]

What does this PR do?

Add support for inputs with qualified names. See fleet implementation in elastic/kibana#262138.

This field aims to fix cases of multiple inputs of the same type in policy templates, what starts being common with otelcol. In these cases a name can be used to explicitly correlate inputs in data streams.

Why is it important?

With the introduction of OTel integrations in 3.6 it starts to be common having multiple inputs with the same type in the same policy template. This leads to ambiguous situations, as data streams referring to these inputs by type cannot distinguish between them.

Checklist

• I have added test packages to test/packages that prove my change is effective.
• I have added an entry in spec/changelog.yml.

Related issues

• Kibana implementation in [Fleet] Support setting explicit names for ambiguous inputs kibana#262138.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cf4302bd-82aa-4416-9593-97766fea5150

📥 Commits

Reviewing files that changed from the base of the PR and between f52133b and 53cdb09.

📒 Files selected for processing (1)

• spec/changelog.yml

✅ Files skipped from review due to trivial changes (1)

• spec/changelog.yml

---

📝 Walkthrough

Walkthrough

Adds a semantic validator that reads manifest.yml and enforces that when a policy_template contains multiple inputs with the same type, each such input must have a non-empty name. Violations produce a structured validation error (code SVR00010). Introduces the name property to the integration inputs schema, registers the validator in the semantic pipeline for integrations, and adds tests, test fixtures, and changelog/documentation updates.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

• 🛠️ Update Documentation: Commit on current branch
• 🛠️ Update Documentation: Create PR

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 53cdb09

cc @jsoriano

[jsoriano]

test integrations

[elastic-vault-github-plugin-prod]

Created or updated PR in integrations repository to test this version. Check elastic/integrations#18309

[teresaromero]

would this be 3.6.1?

[jsoriano]

I would like to allow this from 3.6.0.