This is a follow-up to my previous PR #37359, which added AuthenticationTokenCreatedEvent to the new authenticator-based security system to inspect the security token before it becomes effective to the security system. It adds the passport that was used to generate that token to the event, so that it can be inspected as well.

Reasoning:

1. It makes the event more aligned with other security events (which are also providing the passport)
2. I see valid use-cases when you'd want to look into the passport/badges to decide if you'd want to make modifications to the security token. @Seldaek mentioned to me in Document how to bypass 2FA entirely in a given context scheb/2fa#74 that he'd like to have the ability to add a badge from his custom authenticator class, which then influences 2fa being triggered or not. Having the passport in the event would make that a straight forward task.

I would like to add this to Symfony 5.3, since @wouterj plans to stabilize the authenticator security system for that release, so I believe this is worth adding it now rather than later. The constructor change could be considered a BC break, but since authenticator system is experimental, I believe it's fair to make that change now before declaring it "stable".