Display file permission changes next to filenames

[Copilot]

Closes desktop#11685

Description

When files have only permission changes (e.g., chmod +x), Desktop displayed misleading messages like "Only whitespace changes found" with no indication of what actually changed.

This PR has been rebased onto the development branch and properly integrates with upstream changes including submodule status tracking, rename score features, and path highlighting functionality.

Implementation

• Status parsing: Extract mode fields (mH, mI, mW) from existing git status v2 output, compare HEAD→index or index→working tree based on change location
• Data model: Add optional oldMode/newMode to PlainFileStatus and CopiedOrRenamedFileStatus, alongside upstream's submoduleStatus and renameIncludesModifications fields
• UI rendering: Display mode changes as (100644 → 100755) next to filename in PathLabel component, integrated with upstream's span-based rendering and matches prop
• Styling: Subtle gray text at 0.7 opacity, 0.9em font size
• Testing: Added 3 unit tests for mode change parsing in index, working tree, and unchanged scenarios

The mode information flows from status parser → file status model → UI without additional git calls. Handles all status types (Modified, New, Renamed, Copied, Deleted). Changes are properly merged with upstream features for submodule tracking and rename detection.

Screenshots

Before: File with permission change shows no indication

✓ script.sh [M]

After: Permission change clearly visible

✓ script.sh (100644 → 100755) [M]

Release notes

Notes: When files have only permission changes, the mode change (e.g., 100644 → 100755) now displays next to the filename in the changes list.

Original prompt

desktop#11685
Addressed this issue by displaying the permission index changes next to the file name

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[say25]

@copilot rebase these changes off the default branch

[Copilot]

@copilot rebase these changes off the default branch

I've rebased the changes onto the development branch (upstream/development). The commits have been successfully rebased and merged with the latest upstream changes including submodule status tracking and rename score features.

The new commit is 1d3030a which includes all the permission display changes properly merged with the upstream code. However, I'm unable to force push the rebased branch due to authentication constraints with the git push command.

To complete the rebase, you'll need to manually force push the local copilot/add-permission-index-display branch to origin.