[Cloud] Extend metadata

[afharo]

Summary

Related to #188562

We are missing some information that should come in our telemetry and we'd like to use in our feature flag evaluation contexts:

• Organization ID: The Elastic Cloud Organization that owns the deployment/project
• Orchestrator Target: On Serverless, whether it's a canary or non-canary project.

This PR adds the config to accept both.

cc @elastic/platform-analytics as there are 2 new fields that will be included in our telemetry:

• EBT: context.organizationId and context.orchestratorTarget
• Snapshot telemetry: stack_stats.kibana.plugins.cloud.[organizationId,orchestratorTarget]

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 5988623

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
cloud	19	20	+1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
cloud	6.6KB	7.1KB	+485.0B

Unknown metric groups

API count

id	before	after	diff
cloud	78	81	+3

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @afharo

[SiddharthMantri]

Security changes LGTM!