Az.Tools.Predictor refactor and performance improvement.

[kceiw]

Description

There are a few things going on during the refactor: telemetry, readability, and performance.

1. Replace Tuple/ValueTuple with more meaningful types that don't use 'Item1' and 'Item2'.
2. Replace Newtonsoft Json library with the built-in System.Text.Json.
3. Reformat the telemetry events. Combine the error events with the normal event. Just have a field in the event to indicate if there is an exception or not.
4. Collect the event if the http request to the server has been sent or not. The content isn't collected.
5. Transform data format and send telemetry event in a worker in the default thread pool. This can also improve the performance since that removes the burden on the thread that's handling callback from PSReadLine.
6. Validate parameter values and also catch http response error early instead of when we try to parse the response content.
7. Remove duplicate parsing on the user input.
8. Reduce string manipulation.

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • 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 -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • {Please put the link here}
  • the markdown help files have been regenerated using the commands listed here

[mirdaki]

Looks good to me!

[baopingz]

nit: just return AzurePSDataCollectionProfile.Instance.EnableAzureDataCollection

[baopingz]

looks good.