Revert: Fix getCallerBaggagePairs userId fallback

[fpfp100]

Summary

Reverts #250.

The ingest service only accepts GUIDs for user.id. Any non-GUID value gets replaced with an all-zeros GUID (00000000-0000-0000-0000-000000000000). Allowing non-GUID values as userId (via the aadObjectId → agenticUserId → from.id fallback chain) breaks downstream scenarios that expect an AAD object ID.

Test plan

• Verify existing tests pass
• Confirm userId is only set from aadObjectId again

🤖 Generated with Claude Code

Note

The original PR will not take effect since UPN (non-GUID) values are always ignored by the ingestion service.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Reverts the previously-added userId fallback chain in OpenTelemetry baggage generation so user.id is only populated from aadObjectId, preventing non-GUID values from being sent to ingest.

Changes:

• Update getCallerBaggagePairs to set user.id exclusively from from.aadObjectId
• Remove/adjust tests that asserted fallback to agenticUserId / from.id
• Update Jest config by removing the @microsoft/agents-a365-observability-hosting moduleNameMapper entry

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
tests/observability/extension/hosting/TurnContextUtils.test.ts	Removes tests that asserted userId fallback behavior
tests/observability/extension/hosting/BaggageBuilderUtils.test.ts	Updates expectation so user.id is not emitted when aadObjectId is absent
tests/jest.config.cjs	Removes Jest moduleNameMapper for the hosting package
packages/agents-a365-observability-hosting/src/utils/TurnContextUtils.ts	Reverts user.id to only use aadObjectId