Changes for Telemetry in Azure Test Plan Task

[adityashahms]

Task name: AzureTestPlanV0

Description: Adding CI telemetry to drive usage metrics

Documentation changes required: (Y/N) N

Added unit tests: (Y/N) N

Attached related issue: (Y/N) N

Checklist:

• Task version was bumped - please check instruction how to do it
• Checked that applied changes work as expected

Testing:

• Sample JSON Body Object for Maven:

{
  "builduri": "vstfs:///Build/Build/553",
  "buildid": "553",
  "TestSelector": "automatedTests,manualTests",
  "totalNumOfManualTestPoint": 3,
  "totalNumOfAutomatedTestPoint": 4,
  "totalNumOfTestSuites": 1,
  "manualTestFlowReturnCode": 0,
  "isJavaMavenExecution": true,    // Incase of multi-language. We would have the rest of the language objects as well
  "automatedTestFlowReturnCode": 1
}

• Pipeline Run
  
• Run Information and Result Breakdown
  This information is available from Test Run Feature Telemetry and PublishTestResult Telemetry since we have leveraged APIs and PTR library directly.

[adityashahms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[eswarnathp]

Added comments

[eswarnathp]

lgtm