Symfony version(s) affected: 4.4.0

Description
Until now, if you have a Guard authenticator, its supports() method will be called on every request. However, with anonymous: lazy under your firewall, that no longer happens.

Maybe that's intended? If it is, I think anonymous: lazy can't be used as the default config in the security.yaml recipe, as it creates a very different experience.

How to reproduce
Reproducer: https://github.com/weaverryan/symfony-anonymous-lazy-reproducer

Basically, create an authenticator on a new project and access any URL. It will not be executed (because anonymous: lazy is the default setting in the recipe).

Possible Solution
I'm not sure if this is a bug with anonymous: lazy or if we should revert the recipe back to anonymous: true.

Additional context
Caught by MakerBundle tests :)