fix(input): select empty-value options by text

[Iams4kura]

Summary

• Fixes: When fill targets a native select option whose visible text matches the requested value but whose DOM value is the empty string, the tool reports success while the previously selected option remains selected.
• Root cause: selectOption tests the option's DOM value for truthiness before calling Locator.fill. An empty string is a valid option value, but the truthiness check skips the fill while optionFound remains true, so the handler returns a false success.

Regression evidence

• Before: npx --yes -p node@24 -c 'node --version && npm run test tests/tools/input.test.ts -- --test-name-pattern=empty.value.by.text' exited 1

• After: npx --yes -p node@24 -c 'node --version && npm run test tests/tools/input.test.ts -- --test-name-pattern=empty.value.by.text' exited 0

Verification

• npx --yes -p node@24 -c 'node --version && npm run test tests/tools/input.test.ts'
• npx --yes -p node@24 -c 'node --version && npm run build'
• npx --yes -p node@24 -c 'node --version && npm run check-format'
• npx --yes -p node@24 -c 'node --version && npm run gen'

The full npm run test was also attempted. On this machine it reaches an
unrelated Chrome 151 Page.captureScreenshot: Page is too large failure; the
same screenshot test fails identically on the exact unmodified base SHA under
Node 24. The complete affected input test suite passes.

Scope

• 2 files changed, +40 / -2 lines

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[Lightning00Blade]

LGTM, thanks!