Stack trace linking for VSTS

[jianyuan]

This PR enables Stack trace linking for VSTS.

Depends on #53584

[codecov]

Codecov Report

Merging #52954 (21678ae) into master (0edd435) will increase coverage by 0.53%.
The diff coverage is 100.00%.

❗ Current head 21678ae differs from pull request most recent head 348eaa9. Consider uploading reports for the commit 348eaa9 to get more accurate results

@@            Coverage Diff             @@
##           master   #52954      +/-   ##
==========================================
+ Coverage   78.84%   79.37%   +0.53%     
==========================================
  Files        5086     4934     -152     
  Lines      219350   207248   -12102     
  Branches    37160    35406    -1754     
==========================================
- Hits       172942   164507    -8435     
+ Misses      40806    37710    -3096     
+ Partials     5602     5031     -571     

Files Changed	Coverage
src/sentry/integrations/mixins/repositories.py	ø
src/sentry/integrations/vsts/client.py	100.00%
src/sentry/integrations/vsts/integration.py	100.00%

[leeandher]

Looks good! Could we also get a test for the project_stacktrace_link endpoint that VSTS links are added to the payload? That is how we can get these links to the frontend.

[jianyuan]

@leeandher The test_get_stacktrace_link test should cover that particular use case.

The project_stacktrace_link endpoint invokes the get_stacktrace_link method here. The existing tests for this endpoint utilise the ExampleIntegration for all their tests rather than a specific integration. Moreover, these tests patch the get_stacktrace_link method to return the URL that the frontend displays.

[leeandher]

Looks great! Tested it locally with no issues! I'll run the CI and merge this early next week 👍

[vercel]

@leeandher is attempting to deploy a commit to the Sentry Team on Vercel.

A member of the Team first needs to authorize it.

[leeandher]

/gcbrun