minor #9336 Rename allowSuccessfulResponse to correct allowCustomResponseCode (hkdobrev)

This PR was submitted for the master branch but it was merged into the 3.4 branch instead (closes #9336).

Discussion
----------

Rename allowSuccessfulResponse to correct allowCustomResponseCode

Introduced in 5f0becf

The functionality was introduced in symfony/symfony#19822.
The method got renamed during code review, but was not updated in the docs.
symfony/symfony#19822 (comment)

Commits
-------

0cda0d5 Rename missing allowCustomResponseCode to correct allowCustomResponseCode

Author: javiereguiluz

reference/events.rst

@@ -236,15 +236,15 @@ response:
 
     If you want to overwrite the status code of the exception response, which
     you should not without a good reason, call
-    ``GetResponseForExceptionEvent::allowSuccessfulResponse()`` first and then
+    ``GetResponseForExceptionEvent::allowCustomResponseCode()`` first and then
     set the status code on the response::
 
-        $event->allowSuccessfulResponse();
+        $event->allowCustomResponseCode();
         $response = new Response('No Content', 204);
         $event->setResponse($response);
 
     The status code sent to the client in the above example will be ``204``. If
-    ``$event->allowSuccessfulResponse()`` is omitted, then the kernel will set
+    ``$event->allowCustomResponseCode()`` is omitted, then the kernel will set
     an appropriate status code based on the type of exception thrown.
 
 .. seealso::