`test_input_performActions* ` e2e test is flaky

[sadym-chromium]

e2e tests of input are flaky. Example:

test_input_performActionsEmitsDragging: https://github.com/GoogleChromeLabs/chromium-bidi/actions/runs/6448243919/job/17509797173?pr=1403

Although the output is really hard to read, the difference is expected and missing the following part at the beginning:

      {
        type: 'object',
        value: [
          [
            'event',
            {
              type: 'string',
              value: 'mousemove',
            },
          ],
          [
            'button',
            {
              type: 'number',
              value: 0,
            },
          ],
          [
            'buttons',
            {
              type: 'number',
              value: 0,
            },
          ],
          [
            'clientX',
            {
              type: 'number',
              value: 630,
            },
          ],
          [
            'clientY',
            {
              type: 'number',
              value: 336,
            },
          ],
        ],
      },

Another example:

test_input_performActionsEmitsPointerEvents: Example: https://github.com/GoogleChromeLabs/chromium-bidi/actions/runs/6548857552/job/17784481994?pr=1443 Related: https://github.com/GoogleChromeLabs/chromium-bidi/issues/1407

[jrandolf]

This is a result of headful mode. The solution is to disable the test in headful.

[sadym-chromium]

This is a result of headful mode. The solution is to disable the test in headful.

Cannot we make the test more flexible, so that it tolerates the fluctuations?

[sadym-chromium]

friendly ping. This causes false-negative CI runs almost daily

[sadym-chromium]

another example: https://github.com/GoogleChromeLabs/chromium-bidi/actions/runs/6509030633/job/17679618738

[sadym-chromium]

The issue addressed, expectations do not tolerate flakiness anymore