add support for appcenter service connections

[paulbehrisch]

All Submissions:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My code follows the code style of this project.
• I ran lint checks locally prior to submission.
• [x ] Have you checked to ensure there aren't other open PRs for the same update/change?

What about the current behavior has changed?

Added appcenter service connection support.
https://docs.microsoft.com/en-us/appcenter/distribution/vsts-deploy

Issue Number:

Does this introduce a change to go.mod, go.sum or vendor/?

• Yes
• No

Does this introduce a breaking change?

• Yes
• No

Any relevant logs, error output, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Other information

This change adds support for app center service connections.

Usage:

resource "azuredevops_serviceendpoint_appcenter" "paul-ios" {
 project_id            = azuredevops_project.project.id
 service_endpoint_name = "foo-org-appcenter"
 description           = "appcenter connection for foo-org"
 apitoken              = "xxxxxxxxx"
}

I copied resource_serviceendpoint_bitbucket.go and modifed accordingly. I noticed that the Bitbucket service connection itself has no tests, and I'm myself not too sure how to write a test for it since it requires an additional service. Could you point me in the right direction?

[xuzhang3]

@paulbehrisch You can find the Bitbucket AccTest and Document here. Acceptance tests are in the internal/acceptancetests directory.

[tmeckel]

@paulbehrisch after the provider has been upgraded to the v6 API the code for service connections has to be changed. So it might be a better approach to finish the PR here before the upgrade is done.