Update dependency enzyme-adapter-preact-pure to v4.1.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
enzyme-adapter-preact-pure	4.0.1 -> 4.1.0

---

Release Notes

preactjs/enzyme-adapter-preact-pure

v4.1.0

Compare Source

• Adds a new shallow renderer that more closely matches the behavior of the
  React 16 shallow renderer. This new renderer can be enabled by importing
  CompatShallowRenderer from enzyme-adapter-preact-pure/compat and passing
  it in the ShallowRenderer Adapter option.

  The previous shallow renderer rendered components into a DOM and modified the
  component's output so that all children return null to prevent rendering
  further down the tree. The compat shallow renderer is a custom implementation
  of Preact's diffing algorithm that only shallow renders the given component
  and does not recurse down the VDOM tree. It's behavior more closely matches
  the React 16 Enzyme adapter and it well suited for migrating an Enzyme test
  suite from React to Preact.

• Support more return types (e.g. booleans, numbers, BigInts) from components

• Add an option (renderToString) to allow passing in a custom string renderer
  to use for Enzyme's 'string' renderer instead of rendering into the DOM and
  reading the HTML output. It is expected that renderToString from
  preact-render-to-string is passed into this option. This change enables
  using the string renderer in non-DOM environments and more closely matches the
  React adapter's behavior.

• Add a feature flag (simulateEventsOnComponents) for supporting simulating
  events on Components
  #​211

  This new feature flag turns on behavior that enables calling .simulate
  directly on Components. For shallow rendering, this directly calls the
  component's corresponding prop. For mount rendering, it finds the first DOM
  node in the Component, and dispatches the event from it.

  NOTE: This flag changes the behavior of calling simulate on shallow rendered
  host (a.k.a DOM) nodes. When this flag is off, simulate dispatches a native
  DOM event on the host node. When this flag is turned on, simulate directly
  calls the prop of the event handler with arguments passed to simulate.

  The behavior turned on by this flag matches the behavior of the React 16
  Enzyme adapter.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: exercises/a03/my-project/package-lock.json

npm notice 
npm notice New major version of npm available! 8.19.3 -> 9.2.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.2.0>
npm notice Run `npm install -g npm@9.2.0` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: my-project@0.0.0
npm ERR! Found: jest@29.3.1
npm ERR! node_modules/jest
npm ERR!   dev jest@"29.3.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"26.x || 27.x" from jest-preset-preact@4.0.5
npm ERR! node_modules/jest-preset-preact
npm ERR!   dev jest-preset-preact@"4.0.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-01-06T01_10_19_142Z-debug-0.log