Checklist for new Mailer/Translation/Notifier bridges

[OskarStark]

          > @OskarStark I'm wondering if we should create a checklist of things we should not forget when adding a new mailer/notifier (and publish it in the docs). WDYT?

Makes sense, if I find some spare time, I will do it.

PS: Another option would be to have dedicated Carsonbot comment with the checklist when a new bridge is added

Originally posted by @OskarStark in symfony/symfony#53573 (comment)

[xabbuh]

Some things I have regular added in the past which are not that obvious (easy to miss):

• add the transport factory to UnsupportSchemeException, UnsupportedSchemeExceptionTest
• add the transport factory to the FACTORY_CLASSES constant of the component's Transport class

[OskarStark]

• The Year in the copyright should be the current year

Mostly copy pasted from old bridges

[OskarStark]

• #[\SensitiveParameter] should be used for sensitive properties

[OskarStark]

• A PR against symfony/symfony-docs repo, maybe with an example (already merged PR)
• A PR against symfony/recipes repo, maybe with an example (already merged PR)

[smnandre]

• Check the FrameworkExtension.php (classes defined in the class maps may be accidentally different than the ones declared in Resources/config/notifier_transports.php (same for the other ones) ?

[javiereguiluz]

Folks, this issue looks mostly related to Symfony code, not docs, right?

[OskarStark]

Yes, but Fabien wants to have a checklist in the docs as first step.

Anyone willing to create an initial PR?