**What's the problem this PR addresses?**

In Node.js v22 import assertions were replaced with import attributes so
we need to add support for those as well.

Fixes #6267

**How did you fix it?**

Added support for the `importAttributes` property.

**Checklist**
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).
- [x] I have set the packages that need to be released for my changes to
be effective.
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.

**What's the problem this PR addresses?**

Preact CLI not only now supports Node.js 18, but _requires_ it:

> Usage Error: This tool requires a Node version compatible with
>=18.12.0 (got 16.20.2).


**How did you fix it?**

> `# Remove when Preact CLI supports Node.js 18`

So I did 🤷 

**Checklist**
<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).

<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [x] I have set the packages that need to be released for my changes to
be effective.

<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.

**What's the problem this PR addresses?**

preact-cli is no longer maintained, ref
#5780 (comment)

**How did you fix it?**

Removed the e2e test for it.

**Checklist**
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).
- [x] I have set the packages that need to be released for my changes to
be effective.
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.

Co-authored-by: Maël Nison <nison.mael@gmail.com>

**What's the problem this PR addresses?**

Vitest is increasingly important tool in JS ecosystem. While nowhere
near "industry standard", it's [quickly gaining
traction](https://npmtrends.com/vitest).

...

**How did you fix it?**

Copy Jest's E2E and "migrate" it to Vitest.
...

**Checklist**
<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [ ] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).

<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [ ] I have set the packages that need to be released for my changes to
be effective.

<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [ ] I will check that all automated PR checks pass before the PR gets
reviewed.

**What's the problem this PR addresses?**

The primary reason for v4 update is that v4 uses Node 20 runtime, as
opposed to Node 16 in v3.

...

**How did you fix it?**
<!-- A detailed description of your implementation. -->

...

**Checklist**
<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [ ] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).

<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [ ] I have set the packages that need to be released for my changes to
be effective.

<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [ ] I will check that all automated PR checks pass before the PR gets
reviewed.

Saw a bunch of warnings while checking a log, apparently these versions
use node 16 which is deprecated, and the v3 of upload-artifact and
download-artifact will stop working in November.

**What's the problem this PR addresses?**

The Gatsby development server test has been timing out in the CI for
months now, though it passes locally.

**How did you fix it?**

Disable to so we notice when the build stops working.

**Checklist**
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).
- [x] I have set the packages that need to be released for my changes to
be effective.
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.

**What's the problem this PR addresses?**

The PnP compatibility patch for TypeScript doesn't apply to
`typescript@5.5.2`.

Ref microsoft/TypeScript#35206

**How did you fix it?**

Rebased it.

**Checklist**
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).
- [x] I have set the packages that need to be released for my changes to
be effective.
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.

| Package name | Version |
| --- | --- |
| `@yarnpkg/cli` | `3.8.3` |
| `@yarnpkg/plugin-pnp` | `3.2.16` |
| `@yarnpkg/pnp` | `3.3.8` |
| `@yarnpkg/plugin-compat` | `3.1.20` |