Feat(UI): Search bar in image info code tabs and add vertical margins for improved UX in Recall Parameters tab.

[DustyShoe]

Summary

This PR adds a Search bar to the Image Info Viewer on tabs containing code-like text.
It simplifies searching through large metadata / workflow / graph blocks for specific items.

After entering a keyword, all matching instances are highlighted.
Search is case-insensitive.

Additionally, side padding was added to improve UX on Info tabs, primarily on the Recall Parameters tab.
Previously, navigation arrows could overlap the Recall Parameter buttons when prompts were extremely long or the window size was small.

Before:

After fix:

Related Issues / Discussions

Brief discussion on Discord: https://discord.com/channels/1020123559063990373/1020123559831539744/1462973199443689608

Also closes:
#8775

QA Instructions

Search Bar

1. Open an image with populated Metadata / Workflow / Graph.
2. Navigate to any text-based Info tab.
3. Verify the Search bar is visible.
4. Enter a keyword present in the text.
5. Verify all occurrences are highlighted.
6. Verify the search is case-insensitive.
7. Clear the search input and verify highlights are removed.

Recall Parameters – UX / Padding Fix

1. Open an image with an extremely long prompt.
2. Open Recall Parameters tab.
3. Resize the window to a small width.
4. Verify navigation arrows do not overlap Recall Parameter buttons.
5. Verify all buttons remain visible and clickable.

Merge Plan

Likely low‑risk to merge, but a few merge‑conflict hotspots:

• ImageMetadataViewer.tsx is a central file; if main changed tabs/layout/search recently, expect conflicts around the Tab header and DataViewer usage.
• DataViewer.tsx now has controlled search props; if main also touched DataViewer, you might need to reconcile prop signatures.
• NextPrevItemButtons.tsx is a simple change; conflicts only if main adjusted arrow buttons.

Behavioral risks are minimal: search term state is per‑tab and defaulted safely; arrow hit area is intentionally smaller. If main has different spacing conventions, there could be visual diffs rather than runtime errors.

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Tests added / updated (if applicable)
• ❗Changes to a redux slice have a corresponding migration
• Documentation added / updated (if applicable)
• Updated What's New copy (if doing a release after this PR)

[Pfannkuchensack]

Location: [ImageMetadataViewer.tsx:55]

const activeSearchTerm = searchTerms[activeTabIndex] ?? '';
The fallback ?? '' handles undefined, but if a user somehow enters only whitespace, it will still attempt regex search. Not a bug, but spaces-only search might not be intuitive.

[Pfannkuchensack]

Works good.

[DustyShoe]

Oh, snap! Never thought about spaces.

[DustyShoe]

Adjusted the data viewer search highlight to ignore whitespace-only input by trimming before building the regex, so spaces no longer get highlighted across the page.