When using JSON authentication, customizing the success response can be done easily in the corresponding controller, but customizing the logout success is more tiresome and requires to create a listener for it (while still requiring to create a route for it to work).

This PR propose to add the possibility to disable the redirect on successful logout and let the request fallback to the defined route in this case.

This allow customizing both login and logout response in the same place like this:

security:firewalls:main:json_login:check_path:auth_loginlogout:path:auth_logouttarget:~

class AuthControllerextends AbstractController{    #[Route("/login", name:"auth_login")]publicfunctionlogin():Response    {return$this->json($this->getUser());    }    #[Route("/logout", name:"auth_logout")]publicfunctionlogout():Response    {return$this->json(null);    }}

It means I had to remove the Exception in case no logout listener set a response but I don't think it should be considered a BC break since it's an error case that is removed and the corresponding exception was just the baseRuntimeException and thus wasn't specifically catchable.

The only downside is that other logout listeners can't modify the response anymore because it doesn't exists in the event but since this is an opt-in feature I don't think it's a problem.