- Fix infinite recursion in ToolPermissionsSetupPageView by using
  #[derive(IntoElement)] instead of manual impl that called into_any_element()
  recursively

- Add visual test for tool permissions settings UI page (Test 7)
  - Opens settings at agent.tool_permissions path
  - Captures screenshot of the settings window

- Initialize agent_ui and settings_ui in visual test runner
  - Add ThreadStore::init_global via agent_ui::init
  - Set global AppState before subsystem initialization
  - Fixes panic in agent thread tests

- Take two screenshots in tool_permissions visual test:
  1. tool_permissions_settings.png - Settings page with 'Configure Tool Rules' item
  2. tool_permissions_subpage.png - After clicking Configure button to show sub-page

- Simulate click at approximate Configure button position (830, 350)
- Capture screenshots directly without baseline comparison for now

- Add SettingsWindow::navigate_to_sub_page() public method that navigates
  to a sub-page by its json_path, enabling programmatic navigation

- Update visual test to use navigate_to_sub_page('agent.tool_permissions')
  instead of trying to simulate button clicks

- Second screenshot now correctly shows the Tool Permission Rules sub-page
  with all 8 tools (Terminal, Edit File, Delete Path, etc.)

- Redesign tool permissions UI to use nested sub-pages:
  - Main page shows list of tools with 'Configure >' buttons
  - Each tool has its own sub-page with breadcrumb navigation
  - Tool config pages show regex patterns and default mode dropdown

- Add SettingsWindow::push_dynamic_sub_page() for programmatically
  pushing nested sub-pages that aren't in the main pages list

- Each tool config page shows:
  - Always Allow patterns (green)
  - Always Deny patterns (red)
  - Always Confirm patterns (yellow)
  - Default Action dropdown at the bottom

- Update visual test to capture three screenshots:
  1. Settings page with 'Configure Tool Rules' item
  2. Tool list showing all 8 tools with Configure buttons
  3. Individual tool config page (Terminal) showing patterns

- Make pages module and tool render functions public for visual tests

- Remove card borders around sections, use horizontal dividers instead
- Fix text box IDs so cursor is not shared between fields
- Fix hover highlighting to only apply to delete button, not entire row
- Make pattern rows editable text fields that auto-save on Enter
- Add tooltip to delete button ('Delete pattern')
- Swap order of 'Always Confirm' and 'Always Deny' sections

- Add remote/test-support to title_bar dev-dependencies
- Fix unused variable warnings

Add unique ID to each rule section container so the element stack
context is different when rendering nested input fields. This ensures
each section's 'add pattern' text box has a unique global element ID.

The global gitignore file watcher was processing events for any file
in the watched path, not just the actual gitignore file. This caused
errors when unrelated files (like Firefox cookies.sqlite) triggered
filesystem events.

Now we compare the event path against the expected gitignore path
before attempting to load it.

This reverts commit beff62f.

Adds a 'Test Your Rules' section at the top of each tool's permission
configuration page. Users can type a test input (e.g., a command for
the terminal tool) and press Enter to see how it would be handled:
- 'Allowed' (green) - would be auto-approved
- 'Denied' (red) - would be auto-rejected, with reason shown
- 'Confirm' (yellow) - would prompt for confirmation

Uses the production ToolPermissionDecision::from_input code to ensure
accurate results matching actual tool behavior.

The verification feature should always test the configured rules,
regardless of whether always_allow_tool_actions is enabled globally.
This allows users to test their rule patterns even when they have
the global override enabled.

Displays a prominent warning below the test input when the global
'Always allow tool actions' setting is enabled, informing users that
all tools will be allowed regardless of the configured rules.

When the user clears the test input and presses Enter, the
allow/deny/confirm result is now hidden instead of showing
the previous result.

Instead of requiring Enter to be pressed, the verification result
now updates live as the user types. This is done by:
- Reading the editor text directly during render
- Observing the editor to trigger re-render on text changes
- Removing the unused Global-based state management

When clicked, it clears the sub-page stack and searches for the
setting, navigating the user directly to the always_allow_tool_actions
toggle.

Added a proper navigate_to_setting method to SettingsWindow that:
- Clears the sub-page stack
- Finds the page containing the setting by json_path
- Opens and scrolls to that page and item

The 'Always allow tool actions' link now uses this method to properly
navigate to the setting instead of using a search bar hack.

- Add underline to make it clearer it's a link
- Change to white text on hover
- Remove right margin by using div+label instead of Button

Set text_color on the parent div instead of using Label's color,
so the hover style can properly override it.

When testing rules, now displays all matching patterns below the input:
- Each matched pattern shown on its own line with its rule type
  (Always Deny, Always Confirm, Always Allow)
- Patterns that are overridden by higher-priority rules are shown
  with strikethrough (e.g., an Allow rule overridden by a Deny rule)
- Helps users understand why a particular decision was made

- Use buffer font (monospace) for regex patterns in matched list
- Show patterns in white (Color::Default) instead of rule color
- Keep rule type labels in their respective colors

When the user types input that doesn't match any regex patterns,
display a helpful message indicating that the Default Action will
be used instead of showing an empty space.

The matched patterns list already shows which rule caused the denial,
so the 'Command blocked by security rule' message is redundant.

Each tool now shows a brief explanation of how regex patterns are
matched for that specific tool:
- Terminal: explains command splitting (&&, ||, ;, pipes)
- Edit/Delete/Create/Save: explains path matching
- Move: explains source and destination path matching
- Fetch: explains URL matching
- Web Search: explains query matching

# Conflicts:
#	crates/zed/src/visual_test_runner.rs