DRY out AuthorizationsController#render_success

In our own deployment, we have some custom exception handling around
the `create`` method. By calling the more "public" `create` method in
`render_success`, we get to have a _single_ code path that also supports
`skip_authorization?` and `can_authorize_response?`. The code on L35
is identical to L16.  That suggests identical intent, but not always.
This might be coincidental, in which case, the pull request should be
declined.

CHANGELOG.md

@@ -8,6 +8,7 @@ User-visible changes worth mentioning.
 ## main
 
 Add your entry here.
+- [#????] DRY out AuthorizationsController#render_success
 
 ## 5.7.0
 

app/controllers/doorkeeper/authorizations_controller.rb

@@ -32,7 +32,7 @@ def destroy
 
     def render_success
       if skip_authorization? || can_authorize_response?
-        redirect_or_render(authorize_response)
+        create
       elsif Doorkeeper.configuration.api_only
         render json: pre_auth
       else