Implemented live test and integrated into Azure pipeline

[vidai-msft]

Description

Added live test and integrated it in the pipeline.
This PR added the followings for live test.

• Common module of live test - LiveTestUtility
• Common module of test coverage - TestCoverageUtility
• Ingest live test data and test coverage data to Kusto - KustoUtility
• Live test pipeline related functions

1. Script to invoke .ps1 for different PowerShell hosts - InvokeLiveTestCITask.ps1
2. Script to install Az modules based on different sources - InstallLiveTestAzModules.ps1
3. Script to connect Azure environment with service principal - ConnectLiveTestServicePrincipal.ps1
4. Script to invoke each module which has live test file - InvokeLiveTestScenarios.ps1
5. Script to save live test data and test coverage data to Kusto - SaveLiveTestResult.ps1

In addition, for Release build, test coverage is only enabled when TESTCOVERAGE compilation symbol is inserted.
So added one parameter for daily build with the flag TurnOnTestCoverage=true.

Checklist

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
• SHOULD make the title of PR clear and informative, and in the present imperative tense.
• SHOULD update ChangeLog.md file(s) appropriately
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense. Add changelog in description section if PR goes into generation branch.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
  • Create new module from scratch
  • Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
  • Create new resource type which name doesn't use module name as prefix
  • Have design question before implementation
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT introduce breaking changes in Az minor release except preview version.
• SHOULD NOT adjust version of module manually in pull request

[wyunchi-ms]

Do you want to return it or print it?

[vidai-msft]

I want to return the hashtable. Added OutputType()

[wyunchi-ms]

I would like to return it explicitly。