fix(decky): render plugin on SteamOS 3.7.x

[lobinuxsoft]

Summary

CapyDeploy v1.2.0 stopped rendering on SteamOS 3.7.22 + Decky v3.2.3. The plugin loaded backend-side but the QAM showed nothing — the frontend silently fell into Decky's TheError fallback.

Root cause

getLibraryContextMenu() in src/patches/contextMenuPatch.tsx filtered LibraryContextMenu siblings by both createElement AND navigator:. Steam rebuilt React internals; the literal React.createElement is gone (now jsx/jsxs runtime). .find() returned undefined, fakeRenderComponent(undefined) threw TypeError: fun is not a function, the definePlugin callback aborted, and the loader inserted its error fallback {name, version, content: <TheError/>, icon, loadType}. Without a titleView, that shape is invisible in the sidebar.

Fix

• Drop the createElement filter — leaves only navigator:, mirroring decky-steamgriddb (the original source of this pattern, per the comment on line 3) which kept working through the Steam UI update.
• Migrate title: <div/> → titleView: <div/> to match Decky's official Plugin interface for v3.2.x. The legacy title field is no longer in the TS type; it survived only by spread.

Verification

Built locally and deployed to a Steam Deck (SteamOS 3.7.22, Decky v3.2.3). Confirmed via CDP probe of SharedJSContext:

contentTypeName: "CapyDeployPanel"   (was "TheError")
iconTypeName:    "CapyIcon"          (was "FaExclamationCircle")
keys:            ["titleView","content","icon","onDismount"]

Test plan

• User opens QAM on Steam Deck — CapyDeploy panel visible with title and capybara icon
• User opens QAM on OneXFly — same behavior
• Game library context menu still patched (CapyDeploy entry appears on right-click)

Closes #32