docs: note the `:has()` scaling limit in the Interactive apps guide (#95925)
### What?
Adds a "Good to know" to the Interactive apps guide explaining that the
`data-pending` + `group-has-data-pending:`/`has-data-pending:` pattern
compiles to the CSS `:has()` selector, and when to reach for client
state instead.
### Why?
`:has()` is re-evaluated over the anchored subtree whenever the
attribute toggles, so a broad anchor (like the whole board) combined
with a high-frequency interaction can add up. The guide taught the
pattern without noting that scaling limit, so a reader could copy the
board-wide dim into a per-frame interaction and hit style-recalc cost.
### How?
Documentation only. One callout in Step 3, calibrated so the guide's own
board usage stays fine (it toggles only per filter, and dragging
deliberately skips it), and pointing to client state for the
high-frequency case.