Bumps [webrick](https://github.com/ruby/webrick) from 1.8.1 to 1.8.2.
- [Release notes](https://github.com/ruby/webrick/releases)
- [Commits](ruby/webrick@v1.8.1...v1.8.2)

---
updated-dependencies:
- dependency-name: webrick
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [rexml](https://github.com/ruby/rexml) from 3.3.7 to 3.3.9.
- [Release notes](https://github.com/ruby/rexml/releases)
- [Changelog](https://github.com/ruby/rexml/blob/master/NEWS.md)
- [Commits](ruby/rexml@v3.3.7...v3.3.9)

---
updated-dependencies:
- dependency-name: rexml
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Fix documentation issue for fake-timers mentioned in #2625

The docs were out of sync with the fake-timers docs.

* Update dependencies before new patch version

This service is dead.

> Sometime in November 2023, I observed that new packages and package versions uploaded to NPM stopped being updated on RunKit. > I don’t believe this project is being actively maintained anymore, though it would be delightful if that changed.

https://discuss.runkit.com/t/cant-run-on-runkit-unavaible/4976

If we decide to re-introduce something like runkit, let's make it in a way that will
continue to work, despite aquisitions and so on.

See https://howtomarketagame.com/2021/11/01/dont-build-your-castle-in-other-peoples-kingdoms/

Let's remove it for now, so at least the JS console won't have errors.

The repository has been archived. See https://github.com/smeijer/unimported

This crucial part of this workflow was removed in
278e667, we should have removed the entire job.

When running `browser-test` job on `ubunty-latest` the following error is emitted:

```
Error: Failed to launch the browser process!
[1999:1999:0210/184211.279511:FATAL:zygote_host_impl_linux.cc(128)] No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
[0210/184211.290099:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0210/184211.290150:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
```

The root cause of the error is described at https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md

By locking `browser-test` to `ubuntu-22.04`, we can avoid this error, while a more
elegant solution is found.

We are seeing errors uploading coverage reports to codecov:

```
Rate limit reached. Please upload with the Codecov repository upload token to resolve issue
```

I've added a repository token, as instructed in https://docs.codecov.com/docs/adding-the-codecov-token.

This changeset should fix the upload issue.