build(deps): bump tar-fs and @web/test-runner in /frontend

[dependabot]

Bumps tar-fs to 3.1.2 and updates ancestor dependency @web/test-runner. These dependencies need to be updated together.

Updates tar-fs from 2.1.1 to 3.1.2

Commits

• 522415f 3.1.2
• c6206bb fix missing xfs and tweaks
• 0aa57de 3.1.1
• 0bd54cd expand check
• cb1c571 3.1.0
• 374460e add optional disablement of symlink validation (#119)
• 5bfe6df 3.0.10
• 63e12f9 bare support
• 2ceedf4 3.0.9
• 647447b check windows tweak (#115)
• Additional commits viewable in compare view

Updates @web/test-runner from 0.15.3 to 0.20.2

Release notes

Sourced from @​web/test-runner's releases.

@​web/test-runner@​0.20.2

Patch Changes

• 7aedbaa: Summary Reporter - re-enabled error reporting and made option to disable browser logs and error reporting in this reporter

@​web/test-runner-chrome@​0.18.1

Patch Changes

• 79b0ba4: This changeset removes the Puppeteer/Chrome focus browser patches that shouldn't be needed anymore, and can cause instability.

  The patches were added quite a while ago, and the upstream issues should be resolved in Chromium. See: https://issues.chromium.org/issues/40272146.

  Also see: puppeteer/puppeteer#10350.

  The patches are currently also resulting some instability of web test runner. That is because the patch calls an exposed function from inside the browser, while navigation later on during stopSession can happen; breaking the handle for retrieving function call arguments passed to the exposed function.

  Puppeteer team found this issue and also landed a fix to improve the failure mode here. See: puppeteer/puppeteer#13759

@​web/test-runner@​0.20.1

Patch Changes

• 24e3290: Improve debug message for test runner uncaught exceptions

  This should make debugging easier. It wasn't very easy to figure out where the errors originated from (because of how the actual uncaught exception only happened with many concurrent builds inside a sandbox environment that is hard to debug).

• Updated dependencies [79b0ba4]

  • @​web/test-runner-chrome@​0.18.1

@​web/test-runner-chrome@​0.18.0

Minor Changes

• 86eaa21: Upgrade puppeteer version to v24

@​web/test-runner@​0.20.0

Minor Changes

• 86eaa21: Upgrade puppeteer version to v24

... (truncated)

Changelog

Sourced from @​web/test-runner's changelog.

0.20.2

Patch Changes

• 7aedbaa: Summary Reporter - re-enabled error reporting and made option to disable browser logs and error reporting in this reporter

0.20.1

Patch Changes

• 24e3290: Improve debug message for test runner uncaught exceptions

  This should make debugging easier. It wasn't very easy to figure out where the errors originated from (because of how the actual uncaught exception only happened with many concurrent builds inside a sandbox environment that is hard to debug).

• Updated dependencies [79b0ba4]

  • @​web/test-runner-chrome@​0.18.1

0.20.0

Minor Changes

• 86eaa21: Upgrade puppeteer version to v24

Patch Changes

• Updated dependencies [86eaa21]
  • @​web/test-runner-chrome@​0.18.0

0.19.0

Minor Changes

• b546e8b5: Upgrade puppeteer-core and puppeteer to v23

Patch Changes

• Updated dependencies [b546e8b5]
  • @​web/test-runner-chrome@​0.17.0

0.18.3

Patch Changes

• 6914f3b6: Show suites names for summaryReporter when flatten option is true

0.18.2

... (truncated)

Commits

• 9645344 Version Packages
• 61260d5 Turned error reporting back on by default to match old behviour before it was...
• 4fa7523 add back broken error reporting and make log reporting optional
• db00ed5 Version Packages
• 24e3290 refactor: improve debug message for test runner uncaught exceptions
• f00a581 Version Packages
• fcb71cd Version Packages
• 8834ad8 Version Packages
• d5ae228 Version Packages (#2803)
• 9a88d83 Version Packages (#2774)
• Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[teolemon]

@dependabot rebase

[dependabot]

Superseded by #419.