fix(azure-provider): handle renamed files as new files

[med8bra]

User description

This fixes a bug when azure-provider tries to fetch original content of a renamed file and fails since the file doesn't exist in base yet. Also handles case when diff_type includes multiple actions as edit, rename.

This can be improved to fetch the actual old content using the old path before renaming, but IMO for azure devops since its dying anyway, this fix should be enough.

---

PR Type

Bug fix

---

Description

• Fixed handling of renamed files in Azure DevOps provider.

• Addressed cases where diff_type includes multiple actions like edit, rename.

• Ensured renamed files are treated as new files for content fetching.

---

Changes walkthrough 📝

	Relevant files
Bug fix	azuredevops_provider.py Fix handling of renamed files in diff processing                  pr_agent/git_providers/azuredevops_provider.py Updated logic to handle rename in diff_type. Treated renamed files as new files for content fetching. Adjusted conditions for determining file edit type. +2/-2

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Edge Case Verify that the handling of multiple diff types (e.g. 'edit, rename') works correctly in all scenarios, especially when the order of actions varies elif "rename" in diff_types[file]: # diff_type can be `rename` | `edit, rename` edit_type = EDIT_TYPE.RENAMED

[mrT23]

cool