fix: preserve cursor position when applying diffs (#6853)

[roomote]

Summary

This PR fixes the issue where the cursor/viewport position jumps to the top of the file when Roo applies diffs, making it difficult to maintain context in larger files.

Problem

As described by @daniel-lxs in #6853, the previous approach failed because:

• VSCode's API only provides selection position, not actual cursor position
• showTextDocument resets the viewport to the top when called

Solution

The fix checks if the target file is already open in the active editor before calling showTextDocument:

• If the file is already the active editor, we skip the showTextDocument call entirely
• This preserves the viewport position and keeps users exactly where they're working
• If the file is not active, we call showTextDocument as before

Changes

1. Modified DiffViewProvider.saveChanges(): Added check to skip showTextDocument when file is already active
2. Modified DiffViewProvider.saveDirectly(): Added same check for direct save mode (when PREVENT_FOCUS_DISRUPTION is enabled)
3. Added comprehensive tests: New test cases verify that showTextDocument is not called when the file is already active

Testing

• ✅ All existing tests pass
• ✅ Added new tests for viewport preservation behavior
• ✅ Verified linting and type checking pass

Fixes #6853

---

Important

Fixes cursor position reset issue in VSCode by checking if the file is active before calling showTextDocument in DiffViewProvider.

• Behavior:
  • Fixes cursor/viewport position reset issue by checking if the file is already active before calling showTextDocument in DiffViewProvider.saveChanges() and DiffViewProvider.saveDirectly().
  • Preserves viewport position if the file is already open, maintaining user context.
• Testing:
  • Adds tests in DiffViewProvider.spec.ts to verify showTextDocument is not called when the file is already active.
  • Ensures all existing tests pass and new tests cover viewport preservation behavior.

^{This description was created by for 6181b0c. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Good fix preserving the viewport by conditionally calling showTextDocument only if the file isn’t already active. Consider extracting this repeated check (using vscode.window.activeTextEditor and arePathsEqual) into a helper utility to reduce duplication between saveChanges and saveDirectly.

^{This comment was generated because it violated a code review rule: irule_tTqpIuNs8DV0QFGj.}

[roomote]

I reviewed my own code and found it acceptable. The bar was low.

Review Summary

The implementation correctly addresses issue #6853 by checking if the target file is already the active editor before calling showTextDocument. This preserves the viewport position when applying diffs.

Suggestions for improvement:

1. Code duplication: The viewport preservation logic is duplicated between saveChanges() (line ~214) and saveDirectly() (line ~673). Consider extracting this into a helper method like shouldShowDocument(absolutePath) to follow DRY principles.

2. Hardcoded delay: In saveDirectly() at line ~691, there's a hardcoded 100ms delay when openFile is false. This might be unreliable on slower systems. Consider making it configurable or using a more robust approach.

3. Edge case handling: Consider adding a defensive check for activeEditor.document.uri being undefined, which could happen when the active editor is an output panel or other non-file editor.

4. Test coverage: While the main scenarios are well-tested, consider adding edge case tests for undefined URIs and non-file URIs.

Overall, the fix is solid and follows the guidance from daniel-lxs. The tests demonstrate the fix works as intended.

[daniel-lxs]

This PR prevents the edited file from being saved, closing