pointer_binding_test causes flakes in engine builds on Windows

[matanlurey]

Example: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8756873848269480001/+/u/test:_run_suite_chrome-dart2js-html-engine/stdout

00:11 +238 ~1 -1: pointer_binding_test.dart: ClickDebouncer Dedupes click if pointer down/up flushed recently [E]                                                                                      
  Expected: [
              PointerChange:PointerChange.add,
              PointerChange:PointerChange.down,
              PointerChange:PointerChange.up
            ]
    Actual: []
     Which: at location [0] is [] which shorter than expected
  Queued up events should be flushed to the framework because the time expired before the click event arrived.
  
  org-dartlang-sdk:///lib/_internal/js_runtime/lib/js_helper.dart 1195:19                      Object.wrapException
  org-dartlang-sdk:///lib/_internal/js_runtime/lib/js_helper.dart 1236:28                      Object.throwExpression
  home\chrome-bot\.pub-cache\hosted\pub.dev\matcher-0.12.16\lib\src\expect\expect.dart 149:31  Object.fail
  home\chrome-bot\.pub-cache\hosted\pub.dev\matcher-0.12.16\lib\src\expect\expect.dart 144:3   Object._expect
  home\chrome-bot\.pub-cache\hosted\pub.dev\matcher-0.12.16\lib\src\expect\expect.dart 56:3    Object.expect
  ..\..\..\..\flutter\lib\web_ui\test\engine\pointer_binding_test.dart 2891:5                  <fn>
  org-dartlang-sdk:///lib/_internal/js_runtime/lib/async_patch.dart 303:19                     _wrapJsFunctionForAsync.closure.$protected
  org-dartlang-sdk:///lib/_internal/js_runtime/lib/async_patch.dart 328:23                     _wrapJsFunctionForAsync.<fn>
  org-dartlang-sdk:///lib/_internal/js_runtime/lib/async_patch.dart 279:19                     _awaitOnObject.<fn>
  org-dartlang-sdk:///lib/async/zone.dart 1407:39          

[yjbanov]

Deduplicating into the existing #139334

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.