… favor of mapped route parameters (nicolas-grekas)

This PR was merged into the 7.1 branch.

Discussion
----------

[DoctrineBridge] Deprecate auto-mapping of entities in favor of mapped route parameters

| Q             | A
| ------------- | ---
| Branch?       | 7.1
| Bug fix?      | no
| New feature?  | yes
| Deprecations? |
| Issues        | Fix #50739
| License       | MIT

Auto-mapping of entities on controllers is a foot-gun when multiple entities are listed on the signature of the controller.
This is described extensively by e.g. `@stof` in the linked issue and in a few others.

The issue is that we try to use all request attributes to call a `findOneBy`, but when there are many entities, there can be an overlap in the naming of the field/associations of both entities.

In this PR, I propose to deprecate auto-mapping and to replace it with mapped route parameters, as introduced in #54720.

If we go this way, people that use auto-mapping to e.g. load a `$conference` based on its `{slug}` will have to declare the mapping by using `{slug:conference}` instead. That makes everything explicit and keeps a nice DX IMHO, by not forcing a `#[MapEntity]` attribute for simple cases.

Commits
-------

a49f9ea [DoctrineBridge] Deprecate auto-mapping of entities in favor of mapped route parameters

…ameter (eltharin)

This PR was squashed before being merged into the 7.3 branch.

Discussion
----------

[Routing] Add alias in `{foo:bar}` syntax in route parameter

| Q             | A
| ------------- | ---
| Branch?       | 7.3
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| License       | MIT

Since #54720 we can/have to write route parameters with "destination" as slug:bar,

but if we have two properties with same name example :

`/search-book/{name:author}/{name:category}`

we get the error message : Route pattern "/search-book/{name}/{name}" cannot reference variable name "name" more than once.

Actually to prevent this error we have to use MapEntity as :

```php
    public function bookSearch(
        #[MapEntity(mapping: ['authorName' => 'name'])]
        Author $author,
        #[MapEntity(mapping: ['categoryName' => 'name'])]
        Category $category): Response
    {
```

and we have to remove Mapped Route Parameters :

`#[Route('/search-book/{authorName}/{categoryName}')`

This PR proposal is to remove MapEntity attributes and keep Mapped Route Parameters by adding an alias on it :

`/search-book/{authorName:author.name}/{categoryName:category.name}`

With that, EntityValueResolver will search name in author Entity and name in Category Entity.

We can have url with : `{{ path('bookSearch', {authorName: 'KING', categoryName: 'Horror'}) }}`

Commits
-------

4e2c638 [Routing] Add alias in `{foo:bar}` syntax in route parameter

…ameter (eltharin)

This PR was squashed before being merged into the 7.3 branch.

Discussion
----------

[Routing] Add alias in `{foo:bar}` syntax in route parameter

| Q             | A
| ------------- | ---
| Branch?       | 7.3
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| License       | MIT

Since symfony/symfony#54720 we can/have to write route parameters with "destination" as slug:bar,

but if we have two properties with same name example :

`/search-book/{name:author}/{name:category}`

we get the error message : Route pattern "/search-book/{name}/{name}" cannot reference variable name "name" more than once.

Actually to prevent this error we have to use MapEntity as :

```php
    public function bookSearch(
        #[MapEntity(mapping: ['authorName' => 'name'])]
        Author $author,
        #[MapEntity(mapping: ['categoryName' => 'name'])]
        Category $category): Response
    {
```

and we have to remove Mapped Route Parameters :

`#[Route('/search-book/{authorName}/{categoryName}')`

This PR proposal is to remove MapEntity attributes and keep Mapped Route Parameters by adding an alias on it :

`/search-book/{authorName:author.name}/{categoryName:category.name}`

With that, EntityValueResolver will search name in author Entity and name in Category Entity.

We can have url with : `{{ path('bookSearch', {authorName: 'KING', categoryName: 'Horror'}) }}`

Commits
-------

4e2c6386912 [Routing] Add alias in `{foo:bar}` syntax in route parameter

…ameter (eltharin)

This PR was squashed before being merged into the 7.3 branch.

Discussion
----------

[Routing] Add alias in `{foo:bar}` syntax in route parameter

| Q             | A
| ------------- | ---
| Branch?       | 7.3
| Bug fix?      | no
| New feature?  | yes
| Deprecations? | no
| License       | MIT

Since symfony/symfony#54720 we can/have to write route parameters with "destination" as slug:bar,

but if we have two properties with same name example :

`/search-book/{name:author}/{name:category}`

we get the error message : Route pattern "/search-book/{name}/{name}" cannot reference variable name "name" more than once.

Actually to prevent this error we have to use MapEntity as :

```php
    public function bookSearch(
        #[MapEntity(mapping: ['authorName' => 'name'])]
        Author $author,
        #[MapEntity(mapping: ['categoryName' => 'name'])]
        Category $category): Response
    {
```

and we have to remove Mapped Route Parameters :

`#[Route('/search-book/{authorName}/{categoryName}')`

This PR proposal is to remove MapEntity attributes and keep Mapped Route Parameters by adding an alias on it :

`/search-book/{authorName:author.name}/{categoryName:category.name}`

With that, EntityValueResolver will search name in author Entity and name in Category Entity.

We can have url with : `{{ path('bookSearch', {authorName: 'KING', categoryName: 'Horror'}) }}`

Commits
-------

4e2c6386912 [Routing] Add alias in `{foo:bar}` syntax in route parameter