Related GitHub Issue

Closes: #8278

Description

This PR adds tooltips to display full file paths on truncated filenames in file editing/reading notices throughout the chat interface.

Implementation details:

• Added PathTooltip component that wraps StandardTooltip with appropriate styling
• Used maxWidth="min(300px,100vw)" via inline style to reliably override defaults
• Applied [text-wrap:wrap] class to override text-balance behavior
• Added formatPathTooltip helper for consistent path content formatting
• Updated CodeAccordian.tsx, ChatRow.tsx, and BatchFilePermission.tsx to use PathTooltip
• Centralizes tooltip behavior and reduces code duplication

Key design choices:

• Uses inline style for max-width to deterministically override the default max-w-[300px] in TooltipContent
• Uses [text-wrap:wrap] arbitrary property to reliably override the default text-balance CSS
• Centralizes all path tooltip logic in reusable components

Testing:

• All existing tests pass
• Tooltip styling is consistent with other tooltips in the extension
• Responsive width adapts to panel size while preventing tooltip cutoff

Test Procedure

Manual testing steps:

1. Test truncated paths show tooltips:

   • Open Roo Code and start a chat session
   • Ask Roo to read or edit a file with a long path (e.g., src/components/chat/file/with/deeply/nested/structure.tsx)
   • Narrow the chat panel until the filename truncates (shows ellipsis)
   • Hover over the truncated filename in the notice
   • ✅ Verify: Tooltip appears showing the full file path
   • ✅ Verify: Tooltip wraps text to multiple lines without being cut off

2. Test all tooltip locations:

   • Test tooltips on:
     • Single file read operations
     • Single file edit operations
     • Batch file read operations
     • Batch file edit operations
     • Directory listing operations
     • Search operations
     • ✅ Verify: All locations show tooltips with consistent behavior

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: All existing tests pass and functionality works as expected.
• Documentation Impact: No documentation updates required.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshot

Supersedes PR #8797.