fix(locator): prevent click(text, container) from matching the container itself

[DavertMik]

Summary

• Bug: I.click("Description", 'ul[role="tablist"]') clicked the <ul> itself instead of the intended <li role="tab">. Playwright landed the click on whatever child sat at the container's geometric center, so the wrong tab activated while the step still passed — a silent misleading failure.
• Root cause: Locator.clickable.self used ./self::*[contains(normalize-space(string(.)), literal) …]. A container's concatenated string-value always contains every child's text, so the scope element itself matched.
• Fix: narrow self to prefer the deepest descendant whose string-value contains the literal, and only match self when self is that deepest element (or when @value matches — preserves the <input value="…"> case).
• Bonus: extend Locator.clickable.wide with ARIA widget roles (tab, link, menuitem, menuitemcheckbox, menuitemradio, option, treeitem) so clicks hit the semantic element directly rather than relying on bubble-up.

Shared with Puppeteer and WebDriver helpers — both consume Locator.clickable.self unchanged, so they inherit the fix.

Test plan

• Unit suite: npm run test:unit — 597 passed, 0 failed (incl. 5 new clickable.self / clickable.wide xpath tests).
• Playwright helper: npx mocha test/helper/Playwright_test.js --grep "#click" — 15/15 passing (9 pre-existing + #clickXY 3 + invisible 1 + 2 new regressions).
• Puppeteer helper: npx mocha test/helper/Puppeteer_test.js --grep "#click" — 12/12 passing (shares Locator.clickable.self).
• Full Playwright helper suite: 424 passed, 4 failing — the 4 failures are #makeApiRequest (network) and Video & Trace & HAR (Playwright tracing), both unrelated to the click/locator paths.
• Reproduced the bug on this branch before applying the fix: the new #click - tablist regression test fails, confirming the reproduction.

Scenarios covered

• Container with many text-bearing children (the tablist): click now lands on the correct tab — History, Description, Runs, Code template each verified via #selected-tab.
• <a><span>Buy Chocolate Bar</span></a> clicked with 'a' as context: still works (handled first by getByRole('link'), self fallback never reached).
• <div>Submit</div> and <input value="Submit"> with context-is-the-target: self branch still matches.
• [role="tab"] / [role="menuitem"] directly matched by wide — semantic click target, no reliance on event bubbling.

🤖 Generated with Claude Code