[Feature Request] Add git items abstraction and integrate it with pull requests

[Mrnikbobjeff]

Summary

Implement one new tool that integrates with Azure DevOps APIs to enable file reading capabilites. We need this to allow the user to review pull request file content for a specific commit hash.

Tools

Develop the following tools with full parameter support, including optional ones:

get_repository_items: Gets a file content in a repository.

Endpoint: GET https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}/items?path={path}&scopePath={scopePath}&recursionLevel={recursionLevel}&includeContentMetadata={includeContentMetadata}&latestProcessedChange={latestProcessedChange}&download={download}&$format={$format}&versionDescriptor.version={versionDescriptor.version}&versionDescriptor.versionOptions={versionDescriptor.versionOptions}&versionDescriptor.versionType={versionDescriptor.versionType}&includeContent={includeContent}&resolveLfs={resolveLfs}&sanitize={sanitize}&api-version=7.2-preview.1

Rules

1. Adhere strictly to existing project standards and coding conventions.
2. Ensure each tool exposes all API parameters (required and optional).
3. Use the official Azure DevOps Node API to interact with the APIs.

Special treat

If you follow the rules, you'll get candy!

[danhellem]

@Mrnikbobjeff can you provide some examples on how you would use this?

[Mrnikbobjeff]

Sure, my planned prompt is this:
"Read all active pull requests in the repository. For each pull request:

Generate the diff of all changed files.

For every file in the diff, download the full file content.

From the downloaded content, identify the description of the intended task at the beginning of the file.

Analyze the remainder of the file to determine if the described task has been implemented or completed.

If the task has not been completed, create pull request comments that clearly state what is missing and why.

If all tasks appear to be completed, approve the pull request, mark it as successful, and delete the source branch after merging.

Output should consist of:

A list of pull requests with their status.

Any comments generated for incomplete tasks.

A confirmation for approved and merged pull requests."

The diff api is needed to generate the list of changed files one can also see in the pull request files tab in ADO