adding request.options.tools event to 3p

[24anisha]

Add the request.options.tools events to telemetry with the tool schema in the messages_json field.

[github-actions]

Base: e1e6afed Current: dd769272

No screenshot changes.

[Copilot]

Pull request overview

Adds a new enhanced telemetry event to capture the request.options.tools payload (tool schema) for Copilot chat requests, intended for third-party telemetry ingestion.

Changes:

• Emit request.options.tools enhanced telemetry when request.tools is present (both websocket and HTTP request paths).
• Include request correlation fields (headerRequestId, conversationId) and serialize the tools array into a JSON field.

Show a summary per file

File	Description
extensions/copilot/src/extension/prompt/node/chatMLFetcher.ts	Emits the new request.options.tools enhanced telemetry event in both websocket and HTTP request flows.

Copilot's findings

Comments suppressed due to low confidence (1)

extensions/copilot/src/extension/prompt/node/chatMLFetcher.ts:1433

• Same as the websocket path: JSON.stringify(request.tools) can be large (tool schemas), but this enhanced telemetry call doesn’t multiplex/chunk properties, so it can get truncated/dropped. Please use multiplexProperties(...) (and/or chunking) for messagesJson. Also reconcile the messagesJson vs messages_json field naming with the schema referenced in the PR description.

		if (request.tools) {
			this._telemetryService.sendEnhancedGHTelemetryEvent('request.options.tools', {
				headerRequestId: ourRequestId,
				conversationId: telemetryProperties?.conversationId,
				messagesJson: JSON.stringify(request.tools),
			}, telemetryData.measurements);

• Files reviewed: 1/1 changed files
• Comments generated: 2