Add Azure DevOps integration support

[d13]

Add full support for Azure DevOps integrations -- prs, issues, and autolinks (launchpad, start work, etc)

Steps (checkpoints)

• ✅ connection flow, "home" button: Azure DevOps Integration Support - Set Up Azure DevOps Auth Provider and Basic Integration #3976
• ✅ check that prs, issues and autolinks work (make them working): Azure DevOps Integration Support - Add Home PR/Issue Support #3977
• ✅ launchpad: Azure DevOps Integration Support - Add Launchpad Support #3978
• ✅ start work: Azure DevOps Integration Support - Add Start Work Support #3979
• ❓ anything else?

Follow-ups:

• PR search in Launchpad
• same for self-hosted

Additional info

1

some limitations we should be aware of working with Azure and the shared provider library

• Azure PRs don't include a lot of information we get with other providers like GitHub, GitLab. These include mergeable state (need to check with gkdev how they do "Ready to merge" on those PRs), remote info like remote url associated with the PR's head/base refs (those have to be fetched separately), avatar urls for all involved users (have to be fetched separately), and possibly more I haven't seen yet.
• For Azure PRs, "assignees" and "reviewers" are the same thing. There is no way to get "mentioned" PRs or issues.

2

Found out that shared provider library doesn't support head repository info on PRs for Azure DevOps. We need that critically in order to support finding and opening the PR's repo i.e. from Launchpad and other places.

Test Plan: #4024

[Christopher-C-Robinson]

This is closed, and I linked Azure DevOps on the web, but in VS Code, it doesn't seem to be working. I don't see pull requests and the issues linked to the branch something seems off.

[axosoft-ramint]

This is closed, and I linked Azure DevOps on the web, but in VS Code, it doesn't seem to be working. I don't see pull requests and the issues linked to the branch something seems off.

Are you using the pre-release version of the extension? This feature is currently in the pre-release and will be included in the next release version of GitLens.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.