…8.1 classes (ogizanagi)

This PR was merged into the 4.4 branch.

Discussion
----------

Suppress psalm error for UndefinedDocblockClass for PHP 8.1 classes

| Q             | A
| ------------- | ---
| Branch?       | 4.4 <!-- see below -->
| Bug fix?      | no
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets       | #44831 (comment) <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT
| Doc PR        | N/A

Same as #43050 for inlined docblock comments (mainly `class-string<FQCN>`)

Commits
-------

dbc3eea Suppress psalm error for UndefinedDocblockClass for PHP 8.1 classes

…equirements from a \BackedEnum (fancyweb)

This PR was merged into the 6.1 branch.

Discussion
----------

[Routing] Add EnumRequirement to help generate route requirements from a \BackedEnum

| Q             | A
| ------------- | ---
| Branch?       | 6.1
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| Tickets       | -
| License       | MIT
| Doc PR        | -

Ref #44831

I'd like to limit a route parameter allowed values to the backed values of an enum to use it in conjunction with the new `\BackedEnum` argument resolver (ie fail from the start).
Also, sometimes, I'd like to limit it only to a subset of the backed values.
I couldn't find a way to do that because enums can't implement `__toString()` and accessing `->value` is not considered a constant operation.
We can leverage the fact that route requirements can be a `\Stringable`.

Before (no enum):
```php
#[Route(path: '/foo/{bar}', requirements: ['bar' => FooEnum::AAA.'|'.FooEnum::BBB])]
```

Allow all enum cases:
```php
#[Route(path: '/foo/{bar}', requirements: ['bar' => new EnumRequirement(Foo::class)])]
```

Allow a subset:
```php
#[Route(path: '/foo/{bar}', requirements: ['bar' => new EnumRequirement(Foo::class, Foo::Aaa, Foo::Bbb)])]
```

Probably not the best solution but I hope we can find something for that use case for 6.1 😄

cc @ogizanagi

Commits
-------

ce87606 [Routing] Add EnumRequirement to help generate route requirements from a \BackedEnum

…equirements from a \BackedEnum (fancyweb)

This PR was merged into the 6.1 branch.

Discussion
----------

[Routing] Add EnumRequirement to help generate route requirements from a \BackedEnum

| Q             | A
| ------------- | ---
| Branch?       | 6.1
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| Tickets       | -
| License       | MIT
| Doc PR        | -

Ref symfony/symfony#44831

I'd like to limit a route parameter allowed values to the backed values of an enum to use it in conjunction with the new `\BackedEnum` argument resolver (ie fail from the start).
Also, sometimes, I'd like to limit it only to a subset of the backed values.
I couldn't find a way to do that because enums can't implement `__toString()` and accessing `->value` is not considered a constant operation.
We can leverage the fact that route requirements can be a `\Stringable`.

Before (no enum):
```php
#[Route(path: '/foo/{bar}', requirements: ['bar' => FooEnum::AAA.'|'.FooEnum::BBB])]
```

Allow all enum cases:
```php
#[Route(path: '/foo/{bar}', requirements: ['bar' => new EnumRequirement(Foo::class)])]
```

Allow a subset:
```php
#[Route(path: '/foo/{bar}', requirements: ['bar' => new EnumRequirement(Foo::class, Foo::Aaa, Foo::Bbb)])]
```

Probably not the best solution but I hope we can find something for that use case for 6.1 😄

cc @ogizanagi

Commits
-------

ce876065ff [Routing] Add EnumRequirement to help generate route requirements from a \BackedEnum