[javascript] Migrate find-elements atom from Closure to TypeScript

[AutomatedTester]

Summary

• Replaces the Google Closure bot.locators.findElements fragment (//javascript/atoms/fragments:find-elements.js) with a self-contained TypeScript IIFE, following the same pattern as get-attribute and is-displayed
• Updates py/BUILD.bazel to consume the new TypeScript-generated file instead of the Closure output
• Adds a QUnit browser test covering all locator strategies

What changed

New files:

• javascript/atoms/typescript/find-elements.ts — TypeScript IIFE that implements all locator strategies without any Closure or external dependencies: css selector, id, class name, tag name, link text, partial link text, name, xpath, and the full relative locator (above/below/left/right/near and straight-* variants with proximity sort matching the Closure original)
• javascript/atoms/typescript/wrap-find-elements-as-global.js — Node script that wraps compiled output as window.bot.locators.typescript.findElements for browser test pages
• javascript/atoms/test/find_elements_typescript_test.html — 18 QUnit tests exercising each strategy in a real browser via the existing closure_test_suite infrastructure

Updated files:

• javascript/atoms/BUILD.bazel — tsc compile, strip-semicolon, global-wrap targets; find-elements-global added to the atoms filegroup
• javascript/atoms/fragments/BUILD.bazel — copy_file target find-elements-typescript with same visibility as the old Closure fragment
• py/BUILD.bazel — find-elements copy_file src switched from find-elements.js to find-elements-typescript.js

Testing

• //py:test/selenium/webdriver/support/relative_by_tests-chrome-bidi — PASSED (this is the primary consumer of findElements in Python; it exercises all relative locator directions including near, above, below, left, right, straight-* variants)
• TypeScript compilation succeeds via bazel build //javascript/atoms:find-elements-typescript-generated
• Two unrelated pre-existing failures in window_tests and api_example_tests are window-position assertions that fail on multi-monitor macOS setups; they are not affected by this change

Notes for reviewers

The findElements atom is used by Python (and Java/Ruby/dotnet — unchanged here) exclusively for RelativeBy locators. The calling convention from Python is:

find_element_js = f"/* findElements */return ({raw_function}).apply(null, arguments); "
self.execute_script(find_element_js, by.to_dict())
# by.to_dict() → {"relative": {"root": {...}, "filters": [{"kind": "above", "args": [element]}]}}

WebElement references in args are deserialized to actual DOM Element objects by the browser before the script runs, matching the behaviour expected by the resolveAnchor function.