[xm_cyber] Add Client Identification Header to all API Requests

[mohitjha-elastic]

Proposed commit message

xm_cyber: set X-XMCYBER-CONNECTOR-NAME-VERSION header for all HTTP requests

The value of the X-XMCYBER-CONNECTOR-NAME-VERSION header is set to 
Elastic-XM-Cyber/x.y.z where x.y.z is the package version if it is available (this is
the case for stacks at or above 9.3), otherwise the version is set to unknown.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

How to test this PR locally

• Clone integrations repo.
• Install the elastic package locally.
• Start the elastic stack using the elastic package.
• Move to integrations/packages/xm_cyber directory.
• Run the following command to run tests.

elastic-package test -v

Related Issues

• Closes [XM Cyber] Add client identification header to all XM Cyber connector API requests #20259

[infra-vault-gh-plugin-prod]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[vera-review-bot]

🟢 No issues across the latest commits 79a2361.

A new commit triggers another review — at most once every 15 minutes. I skip the PR while it's approved or has merge conflicts.

🤖 AI-Generated Review | Vera Review Bot | 📚 Knowledge base: integration-skills

⚠️ Automated review — verify suggestions before applying.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: 79a2361

cc @mohitjha-elastic

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[elastic-vault-github-plugin-prod]

Package xm_cyber - 0.2.0 containing this change is available at https://epr.elastic.co/package/xm_cyber/0.2.0/