Update cuyz/valinor requirement from ^1.12 to ^2.2

[dependabot]

Updates the requirements on cuyz/valinor to permit the latest version.

Release notes

Sourced from cuyz/valinor's releases.

2.2.0

Notable new features

Mapping error messages improvements

Feedback has been improved in mapping error messages, especially the expected signature of the failing nodes.

This gets rid of the infamous ? that was used whenever an object was present in a type, leading to incomplete and misleading messages.

Example of a new message:

final class User
{
    public function __construct(
        public string $name,
        public int $age,
    ) {}
}
(new MapperBuilder())
->mapper()
->map(User::class, 'invalid value');
// Could not map type User. An error occurred at path root: Value
// 'invalid value' does not match array{name: string, age: int}.

Features

• Improve mapping error messages types signatures (ce1b0a)

Bug Fixes

• Prevent undefined values in non-empty-list (9739cd)
• Properly detect nested invalid types during mapping (ad756a)
• Use proper error message for invalid nullable scalar value (b84cbe)

Other

• Add safeguard in type parsing when reading next type (da0de0)
• Improve type parsing error when an unexpected token is found (5ae904)
• Lighten types initialization (6f0b3f)
• Parse iterable type the same way it is done with array (6291a7)
• Rework how type traversing is used (20f17f)
• Set default exception error code to unknown (c8ef49)

Commits

• 35470e5 release: version 2.2.0
• ce1b0a2 feat: improve mapping error messages types signatures
• 9739cd0 fix: prevent undefined values in non-empty-list
• a9d3f16 chore(deps): update infection/infection
• 86c77a5 qa: show Infection mutations in console output
• 6e88473 qa: force 100% MSI in pull request pipeline
• ad756ae fix: properly detect nested invalid types during mapping
• 20f17fb misc: rework how type traversing is used
• da0de01 misc: add safeguard in type parsing when reading next type
• 5ae9044 misc: improve type parsing error when an unexpected token is found
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)