fix: React selector detection in findElements for Locator objects

The findElements function was checking locator.react directly, but when
called from findClickable, the locator is wrapped in a Locator object
which stores the react property in locator.locator.react instead.

This commit:
1. Updates findElements to check for React locators in multiple ways:
   - locator.type === 'react' (Locator object)
   - locator.locator?.react (Locator object with nested locator)
   - locator.react (raw locator object)

2. Updates findReactElements to handle both Locator objects and raw
   locator objects by checking for locator.locator property first

Fixes: React selector tests now passing
Test results: 42/44 passing (100% of non-skipped tests)

Author: kobenguyent

lib/helper/Puppeteer.js

@@ -2872,7 +2872,10 @@ export default Puppeteer
  * @returns {Promise<Array>} Array of ElementHandle objects
  */
 async function findElements(matcher, locator) {
-  if (locator.react) return findReactElements.call(this, locator)
+  // Check if locator is a Locator object with react type, or a raw object with react property
+  const isReactLocator = locator.type === 'react' || (locator.locator && locator.locator.react) || locator.react
+  if (isReactLocator) return findReactElements.call(this, locator)
+  
   locator = new Locator(locator, 'css')
 
   // Use proven legacy approach - Puppeteer Locator API doesn't have .all() method
@@ -3389,7 +3392,9 @@ function _waitForElement(locator, options) {
 }
 
 async function findReactElements(locator) {
-  const resolved = toLocatorConfig(locator, 'react')
+  // Handle both Locator objects and raw locator objects
+  const resolved = locator.locator ? locator.locator : toLocatorConfig(locator, 'react')
+  this.debug(`Finding React elements: ${JSON.stringify(resolved)}`)
 
   // Use createRequire to access require.resolve in ESM
   const { createRequire } = await import('module')