Add tool mcp_ado_repo_get_pull_request_changes

[posidron]

Replace by description of the work done

GitHub issue number

Associated Risks

Replace by possible risks this pull request can bring you might have thought of

✅ PR Checklist

• I have read the contribution guidelines
• I have read the code of conduct guidelines
• Title of the pull request is clear and informative.
• 👌 Code hygiene
• 🔭 Telemetry added, updated, or N/A
• 📄 Documentation added, updated, or N/A
• 🛡️ Automated tests added, or N/A

🧪 How did you test it?

Replace with use cases tested and models used

[codecov-commenter]

Codecov Report

❌ Patch coverage is 79.74684% with 16 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (main@c978428). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
src/tools/repositories.ts	79.74%	3 Missing and 13 partials ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #801   +/-   ##
=======================================
  Coverage        ?   93.35%           
=======================================
  Files           ?       16           
  Lines           ?     1761           
  Branches        ?      372           
=======================================
  Hits            ?     1644           
  Misses          ?       31           
  Partials        ?       86           

Flag	Coverage Δ
unittests	93.35% <79.74%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[danhellem]

@posidron this PR has been in draft for over 3 weeks. If we do not see any progress by 1/13, we will go ahead and close the PR. Hope to hear from you soon.

Also please follow guidance as documented in Contributions file. We request an Issue be created first for approval before a PR will be considered.

[danhellem]

Closing this draft due to no response from author

[posidron]

@danhellem I created the issue here: #868

[danhellem]

@posidron I think we agree that this is a good idea. @nikolapeja6 on our team is going to spend some time on this reviewing your PR and testing to make sure the tool works at scale with large PRs. It will be a week or two before have any results.

Stand by