fix: use W3C WebDriver text format for element value input

[daifma]

Problem

The driver sends {"value": ["text"]} (legacy JSON Wire Protocol format) in postValue() calls,
but Selenium 4+ with ChromeDriver requires {"text": "string"} per the
W3C WebDriver specification.

This causes setValue(), attachFile(), and file upload to silently fail or throw errors
when used with Selenium 4 standalone Chrome.

Fix

Replace all three occurrences of the legacy format with W3C-compliant format:

# setValue() — file input (line ~635)
- $element->postValue(array('value' => array(strval($value))));
+ $element->postValue(['text' => strval($value)]);

# setValue() — text input/textarea (line ~652)
- $element->postValue(array('value' => array($value)));
+ $element->postValue(['text' => $value]);

# attachFile() (line ~777)
- $element->postValue(array('value' => array($remotePath)));
+ $element->postValue(['text' => $remotePath]);

How to reproduce

1. Use selenium/standalone-chrome:latest (Selenium 4+)
2. Configure Behat with ediasoft/mink-selenium4-driver
3. Try to fill a text field with $session->getPage()->fillField('name', 'value')
4. Observe: ChromeDriver rejects the {"value": [...]} payload

References

• W3C WebDriver spec — Element Send Keys: https://www.w3.org/TR/webdriver2/#element-send-keys
• The text field is the W3C-compliant key for sending keystrokes to an element

[daifma]

@ShuCh3n PLZ review !

[daifma]

@ShuCh3n ?