Correcting bugs for provider and JSON login

On lines 501 and 502 I propose this change, because it confused me so much which provider to use, and in the case that you are explaining there you should use earlier configured app_user_provider, not users_in_memory.

On line 1043 I had a problem that $user is always null until I deleted the "?User" from parameters. I think that PHP gets confused here with the way it is written. And to say that now with that part removed everything works fine.

Thanks in advance and I hope that I contributed even a little as this is.

Author: KosticDusan4D

security.rst

@@ -498,7 +498,8 @@ will be able to authenticate (e.g. login form, API token, etc).
                     security: false
                 main:
                     lazy: true
-                    provider: users_in_memory
+                    # provider that you set earlier inside providers
+                    provider: app_user_provider
 
                     # activate different ways to authenticate
                     # https://symfony.com/doc/current/security.html#firewalls-authentication
@@ -1039,7 +1040,7 @@ token (or whatever you need to return) and return the JSON response:
       {
           #[Route('/api/login', name: 'api_login')]
     -     public function index(): Response
-    +     public function index(#[CurrentUser] ?User $user): Response
+    +     public function index(#[CurrentUser] $user): Response
           {
     +         if (null === $user) {
     +             return $this->json([