Client Telemetry And Diagnostics : Adds VMId or Unique Id in payload

[sourabh1007]

Description

1. Add machineId information in client telemetry payload and request diagnostics.
   a) For Azure Instance : it will be vmId from Azure Instance Metadata API call with prefix vmId:
   b) Otherwise:
   i) It will have hashedMachineId: + <hashedMachineName>
   ii) If it throws exception, uuid: <generated uuid>
2. No retry policy for VM Metadata API call, till now Default Policy were retrying if call fails.
3. No retry policy for Client Telemetry API call.

Use Cases for Client Telemetry:

a) Helpful to identify if any particular machine is having issue.
b) We can corelate this information with Compute Kusto/Networking Team (any other team outside cosmos db sdk)

Use Cases for Request Diagnostics:

a) In case of vmid, We can corelate this information with Compute Kusto/Networking Team (any other team outside cosmos db sdk)
b) It will be helpful to identify if all the requests are coming from same machine or different machine. (if cx provides bunch of request diagnostics)
c) In case of uuid, this information won't be helpful much.

For Azure Instance:

Client Telemetry

Request Diagnostics

For Non-Azure Instance:

Client Telemetry

Request Diagnostics

Client Telemetry

Request Diagnostics

Type of change

• [] New feature (non-breaking change which adds functionality)

Closing issues

To automatically close an issue: closes #3096

[FabianMeiswinkel]

The vmId should be added to request diagnostics as well

[FabianMeiswinkel]

LGTM except for few small comments

[FabianMeiswinkel]

LGTM - thanks