fix(lint): detect optional managed media calls

[user-github-me]

Optional chaining currently bypasses imperative_media_control: video?.play(), video.play?.(), and optional calls on direct DOM lookups pass lint even though HyperFrames must own managed-media playback. The same rule also reports ordinary calls printed inside strings, comments, templates, or regular expressions.

Extend the existing play/pause matchers to optional property access and optional calls. Use the existing JavaScript code mask to check that bindings and controls begin in executable code, retaining real calls inside template interpolations. Existing finding messages, snippets for ordinary calls, and media IDs are preserved.

Validation:

• 21 regression cases cover variables, direct ID/selector lookups, optional calls, template interpolation, quoted examples, and non-media controls. The initial 17 cases produced 15 failures on main.
• Full lint suite: 855 passed. CLI project/command/format suites: 99 passed.
• All 214 shipped example/block compositions produce byte-identical findings to main.
• Built CLI rejects optional calls with the expected error and accepts the quoted-example control. Its strict Chrome check passes with no findings and all five contrast samples passing.
• Lint and CLI builds/typechecks, repository lint, formatting, pre-commit gates, comment checks, deletion guard, and test reachability passed.

No new dependency or runtime playback change.

[jrusso1020]

Confirmed that video?.play() and video.play?.() slip past imperative_media_control on main, even though the plain call is an error. Widening the existing matchers and using the existing JS code mask is a small, consistent fix, and the quoted-example controls are a good addition. The new cases fail on main, and the full lint suite passes.

— Rames