fix(sdk): decode scoped IDs when replaying patches

[user-github-me]

An SDK edit to hf-host/hf-leaf emits a JSON Pointer such as /elements/hf-host~1hf-leaf/text. The patch reader passes that encoded segment to the scoped DOM resolver, so replay, saved overrides, and iframe synchronization lose the edit. Decode element IDs once, in JSON Pointer order, before resolving the target.

The patch format stays the same. Style, text, attribute, timing, hold, and removal patches now replay against the same nested element that the forward edit changed, including literal ~1 IDs.

Validation:

• Reproduced on main: forward style edit succeeded while emitted-patch replay and reopening saved overrides left the nested element unchanged.
• All 14 new regressions failed before the fix; all 621 SDK tests pass afterward, covering emitted patches, override replay, batch rollback, and a literal ~1 ID.
• Built SDK in Chrome 152 with a real iframe: nested text/style edits, undo, redo, iframe reload, saved-override reopening, and event replay all passed; the sibling with the same ID stayed unchanged and no runtime errors occurred.
• SDK build, repository lint, and changed-file formatting passed.

[jrusso1020]

Verified: patch paths escape scoped IDs as JSON Pointer (hf-host~1hf-leaf), but the replay parser hands the escaped segment straight to findById. So replay, saved overrides and batch rollback all miss nested elements. Decoding once, in RFC 6902 order, before resolving is correct and leaves the patch format unchanged. Optional nit: this duplicates decodePathSegment in patches.ts, which could be exported and reused. The tests cover every element patch kind and check that the same-ID sibling stays untouched.

— Rames