Deprecate SensioFrameworkExtraBundle

[codedmonkey]

The SensioFrameworkExtraBundle was once created to add annotation support to controllers for projects using the Symfony framework. In the words of Symfony creator Fabien:

These feature were in a bundle as annotations in phpdocs were controversial back then. Now that we have native annotations, it makes sense to move them to core.

With the hard work from @nicolas-grekas and some other Symfony contributors, most of the functionality from this bundle has now been incorporated into the Symfony core:

• Feature Request [RFC] Abandon FrameworkExtraBundle #44705
• Controller Attributes [HttpKernel] Add ControllerEvent::getAttributes() to handle attributes on controllers #46001
• DateTimeParamConverter [HttpKernel] Add DateTimeValueResolver #45589
• Cache [HttpKernel] Add #[Cache()] to describe the default HTTP cache headers on controllers #46880
• Template [TwigBridge] Add #[Template()] to describe how to render arrays returned by controllers #46906
• IsGranted [Security] Add #[IsGranted()] #46907 (see Improve #[IsGranted] #46912)
• ~Security~ (see comment and Improve #[IsGranted] #46912)
• Entity [DoctrineBridge] Add an Entity Argument Resolver #43854
• ~ParamConverter~ (see comment)

It looks like there's no reason to support this bundle any longer after Symfony 6 LTS is released, so it's time to start discussing the next steps. We're interested to hear if there's still something we missed and thoughts on the best way to help developers migrate away from this bundle.

[fabpot]

I think it's a bit early. But we will probably add deprecation notices in December 22, just after the release of 6.2.

[codedmonkey]

Never too early to start talking about it and let people know about what's coming up haha. :)

[fabpot]

But we don't want to trigger deprecation notices without the possibility to remove them.