useMicrosoftOpenTelemetry a365 config does not expose useS2SEndpoint option

[fpfp100]

Summary

The distro Agent365Exporter supports useS2SEndpoint, but the high-level useMicrosoftOpenTelemetry({ a365: { ... } }) API doesn't expose it. For OBO scenarios, you need to use Agent365Exporter directly instead of the high-level API.

// High-level API — no useS2SEndpoint option available
useMicrosoftOpenTelemetry({
  a365: {
    enabled: true,
    tokenResolver: ...,
    // useS2SEndpoint not available here
  },
});

// Agent365Exporter — useS2SEndpoint is supported
const exporter = new Agent365Exporter({
  tokenResolver: ...,
  useS2SEndpoint: false,  // ✓ works here
  clusterCategory: 'prod',
});

Request

Expose useS2SEndpoint in the useMicrosoftOpenTelemetry({ a365: { ... } }) config for consistency with the Python and .NET distros:

• Python: use_microsoft_opentelemetry(a365_use_s2s_endpoint=True/False)
• .NET: o.Agent365.Exporter.UseS2SEndpoint = true/false

Package

@microsoft/opentelemetry v0.1.0-beta.1

[github-actions]

cc @hectorhdzg @JacksonWeber @lzchen @MSNev @rads-1996 @jeremydvoss

[fpfp100]

Verified that useS2SEndpoint is properly wired through useMicrosoftOpenTelemetry in v1.0.2:

useMicrosoftOpenTelemetry({
  a365: {
    enabled: true,
    tokenResolver: ...,
    useS2SEndpoint: true,  // ✓ works in v1.0.2
  },
});

The chain: A365Options.useS2SEndpoint → A365Configuration → Agent365Exporter({ useS2SEndpoint }) → /observabilityService endpoint.

This was missing in v0.1.0-beta.1 (required manual Agent365Exporter workaround) but is fully supported in v1.0.2.