VPAAMP-102: Fix duplicate res metric key in drmMetadata networkMetrics and documentation

[srikanthreddybijjam-comcast]

Reason for change: Modified res override with dns and updated Documentation.
Test Procedure: Refer Jira ticket VPAAMP-102
Priority: P1

[Vinish100]

Looks good to me 👍

[Copilot]

Pull request overview

This PR addresses a duplicate networkMetrics JSON key in DRM metadata telemetry by renaming the curl “resolve” metric key from res (conflicting with HTTP response) to dns, and updates unit-test validation and public UVE documentation accordingly.

Changes:

• Fix UpdateLicenseMetrics() to emit dns (DNS resolve time) instead of a duplicate res key.
• Add/extend test plumbing to capture networkMetrics JSON from DrmMetaDataEvent and validate all expected keys/values.
• Update AAMP-UVE-API.md to document the corrected networkMetrics schema and examples.

Reviewed changes

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

Show a summary per file

File	Description
drm/AampDRMLicManager.cpp	Fixes the duplicated JSON key by emitting dns for resolve timing and clarifies key meanings.
test/utests/fakes/FakeAampEvent.cpp	Allows tests to intercept setNetworkMetricData() via the global mock delegate.
test/utests/mocks/MockDrmMetaDataEvent.h	Adds setNetworkMetricData() to the mock so tests can capture the JSON payload.
test/utests/tests/AampDRMLicManagerTests/AampDRMLicManagerTestCases.cpp	Adds a new test asserting the complete networkMetrics keyset and values.
AAMP-UVE-API.md	Updates API documentation to reflect the corrected networkMetrics schema and removes the key collision.