Correct OTLP CLI version attribution for scope/service/span fields

[Copilot]

OTLP telemetry currently labels engine version as gh-aw.cli.version (and in scope.version / service.version), while the actual gh-aw CLI version from aw_info.json.cli_version is not surfaced. This makes version-based telemetry grouping misleading.

• Version attribution fix (CLI-first precedence)

  • Updated OTLP version resolution to prefer CLI version for CLI-named dimensions:
    • aw_info.json.cli_version
    • GH_AW_INFO_CLI_VERSION
    • then existing engine/workflow fallbacks (agent_version, version, GH_AW_INFO_VERSION, SHA/unknown where applicable)
  • Applied consistently in:
    • actions/setup/js/send_otlp_span.cjs (setup + conclusion spans)
    • actions/setup/js/otlp.cjs (shared logSpan)
    • actions/setup/js/emit_outcome_spans.cjs (outcome exporter)

• Behavioral consistency across OTLP surfaces

  • Ensures the same resolved version value is used for:
    • span attribute gh-aw.cli.version
    • instrumentation scope.version
    • resource service.version

• Regression coverage updates

  • Updated tests to assert cli_version is preferred over agent_version where both are present:
    • actions/setup/js/send_otlp_span.test.cjs
    • actions/setup/js/otlp.test.cjs
    • actions/setup/js/emit_outcome_spans.test.cjs

// New precedence used for CLI-labeled version dimensions
const scopeVersion =
  awInfo.cli_version ||
  process.env.GH_AW_INFO_CLI_VERSION ||
  awInfo.agent_version ||
  awInfo.version ||
  process.env.GH_AW_INFO_VERSION ||
  process.env.GITHUB_SHA ||
  "unknown";

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.