fix(deps): update dependency nl.jqno.equalsverifier:equalsverifier to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
nl.jqno.equalsverifier:equalsverifier (source)	3.19.4 -> 4.0.7

---

Release Notes

jqno/equalsverifier (nl.jqno.equalsverifier:equalsverifier)

v4.0.7

Fixed

• StringIndexOutOfBoundsException when using forPackage on Windows. (Issue 1106)

v4.0.6

Changed

• EqualsVerifier will issue an error when an entity has lazy fields that should be accessed by their getter, and the getter is final, because in that case it can't perform the check. (Issue 1102)

v4.0.5

Fixed

• When verifying a relaxed equals relation, andUnequalExamples thinks two unequal examples are equal. (Issue 1098)

v4.0.4

Fixed

• Can now test a class with a field whose type is an array of a single value enum. (Issue 1093)

v4.0.3

Changed

• forPackage can now also scan jar files, which is handy for certain kinds of integration tests that run against jar files instead of directories with .class files. (Issue 1078)

v4.0.2

Added

• Support for Kotlin delegates. (Issue 1083)

Changed

• When a Mockito error occurs, the error message now says which mocked method was attempted to call. (Issue 1082)

v4.0.1

Fixed

• A class with field of type EnumMap or EnumSet produces MockitoException when Mockito is present. (Issue 1080)

v4.0

Fixed

• StringIndexOutOfBoundsException when using forPackage on Windows. (Issue 1106)

---

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 was generated by Mend Renovate. View the repository job log.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.