Add a means to test the API

[marcoscaceres]

The API is not currently testable for interop because it's obviously not possible always have a physical Gamepad available (and being pressed) in a continuous integration environment.

It would be great if the spec provided a Web Driver API that allowed:

• connecting a mock gamepad, and specifying or overriding a limited set of details (e.g., id and mapping).
• disconnecting a mock gamepad.
• setting button values on a mock gamepad.
• setting the axis values on a mock gamepad.
• setting possibly other supported aspects of the gamepad.

Once updated, calling getGamepads() would return the updated snapshot of the mock gamepads.

Out of scope would be to provide a means to "playback" a set of button presses.

[sadym-chromium]

connecting a mock gamepad, and specifying or overriding a limited set of details (e.g., id and mapping).
disconnecting a mock gamepad.

Web Bluetooth specifies more or less similar functionality as a WebDriver BiDi extension: https://webbluetoothcg.github.io/web-bluetooth/#bluetooth-simulateAdapter-command

setting button values on a mock gamepad.
setting the axis values on a mock gamepad.

WebDriver BiDi input.performActions command can be extended with input type "gamepad".

setting possibly other supported aspects of the gamepad.

Is there a specific list needs to be automated?