Fix React DOM nesting and prop warnings

[pawelangelow]

What

Fixes React validateDOMNesting console warnings caused by invalid HTML nesting (e.g., <div> inside <p>, <p> inside <p>).

Changes

• Text component nesting: Added component="div" or component="span" prop to Text components that wrap block-level elements, preventing invalid <p> nesting
• VirtualTable: Fixed <div> inside <p> warning by adding component="div" to Text wrapper
• BottomGroupMinimized: Fixed CLI/Profiler button labels by using component="span"
• StreamEntryFields: Created InlineRow styled component with as: 'span' for inline flex layouts
• Various stream views: Added proper component props to Text elements in GroupsViewWrapper, ConsumersViewWrapper, StreamDataViewWrapper
• Other fixes: KeyRowName, KeyRowTTL, KeyRowSize, EditableInput, EditableTextArea, NoKeySelected, ListDetailsTable, DatabasesList, ExploreGuides, Notification, UploadWarning, RiToast

Not Fixed (Out of Scope)

The customColor prop warning on SVG elements comes from the external @redis-ui/icons_multicolor package. This would be handled in a separate PR.

There's one additional warning related to nested buttons inside RediSearchIndexesList. The @redis-ui Accordion component renders a button internally, and when we pass a button as a child, it creates invalid inside nesting. This requires refactoring on the @redis-ui side and will be addressed separately.

Testing

1. Open the app and navigate through different pages (Browser, key details, stream views)
2. Open browser console - no validateDOMNesting warnings should appear
3. Verify all UI elements look and function the same as before

---

Closes N/A

---

[!NOTE]
Addresses widespread React validateDOMNesting warnings and tightens related UI/state handling.

• Standardizes Text usage by setting component="div" or component="span" where wrapping block elements (RiToast, VirtualTable cells/placeholders, key-row Name/TTL/Size, stream views, editable inputs/areas, notifications, upload warning, success messages, bottom group labels)
• VirtualTable: fixes <div>-in-<p> issue and simplifies empty-state rendering
• KeyTree: opens parent nodes using functional state update and guards against empty parents; syncs open state to store
• StreamEntryFields: adds InlineRow (as span) and adjusts inline helper/error text to prevent invalid nesting
• ExploreGuides: centers headings/text; adds key to guide buttons
• DatabasesList: updates selection cell to pass row explicitly for RowSelectionButton

^{Written by Cursor Bugbot for commit 2078473. This will update automatically on new commits. Configure here.}

[github-actions]

Code Coverage - Frontend unit tests

St.❔	Category	Percentage	Covered / Total
🟢	Statements	82.86%	21105/25470
🟡	Branches	68.07%	8885/13053
🟡	Functions	78.04%	5783/7410
🟢	Lines	83.26%	20670/24827

Test suite run success

5487 tests passing in 704 suites.

Report generated by 🧪jest coverage report action from 2078473

[pd-redis]

Not a big deal, but I would use div not span

[pawelangelow]

Valid! The toast message, however, has some wrapper already that is: <p> {everything is rendered here} </p>, so we endup with: <p><div>...</div></p> which triggers a warning.

[pd-redis]

There must be a simpler fix up the chain that is simpler than adding a prop to each Text component here

[pawelangelow]

I removed a few of them, so WDT now?