Create new client ID for GCM when speaking to Azure Repos

[mjcheetham]

We are currently using the same client ID as Visual Studio for ADAL (this is what GCM Windows also used). We should move to our own client ID, and have it join the Microsoft FoCI.

Question(s): should we join FoCI and become a 1st party app or not? Is consent not something we want to show?

[vtbassmatt]

@mjcheetham this is only for Azure Repos, right? If so, I'll specify that in the title and we'll keep it open but marked "inactive" until we hear from the Repos team.

[mjcheetham]

Correct. Azure Repos only. Updated the title.

[kyle-rader]

Following :)

[mjcheetham]

In order to correctly support WAM (Windows broker) we require a new client ID/first-party application. Removing the inactive tag from this issue.