Add US Gov endpoint for OperationalInsights data plane

[alexeldeib]

Description

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate change log has been updated
• 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:
  • the changes have gone through a cmdlet design review
  • the cmdlet markdown files were generated using the platyPS module

[markcowl]

@alexeldeib Thanks for the contribution, what is the source of these endpoints? Have you been able to successfuly use operational insights cmdlets in Fairfax using these values?

[markcowl]

Thanks for the contribution, what is the source of these endpoints? Have you been able to successfuly use operational insights cmdlets in Fairfax using these values?

[alexeldeib]

Hey Mark, I'm a dev on the team owning the backend service and i'm also the primary driver on our swagger/SDK/cmdlets. Our Fairfax service endpoint wasn't up while the initial work around SDK/cmdlets was picking up. Now that it's up (and we have users who want to query Fairfax), I figured adding the endpoint (following the existing pattern) would make sense. Users there have already been able to use the cmdlet as-is with a custom Add-AzureRmEnvironment (copying all properties from fairfax, with the addition of our two endpoints), while this bakes that manual workaround into code. I'll admit I haven't extensively tested the cmdlets with this change (fairfax access/perms) -- even so, I figured it was a fairly transparent change to simplify an existing user workflow. Let me know what you think!

[markcowl]

on demand: https://azuresdkci.westus2.cloudapp.azure.com/view/PowerShell/job/powershell-demand/778/

[maddieclayton]

@azuresdkci test this please