Destination query parameter should not have precedence over path in redirect

It looks like this is not realy a lupus_ce_renderer but a designed behavior in \Drupal\Core\EventSubscriber\RedirectResponseSubscriber::checkRedirectUrl the destination parameter has precedence and is set as targetUrl on RedirectResponse.

      // Let the 'destination' query parameter override the redirect target.
      // If $response is already a SecuredRedirectResponse, it might reject the
      // new target as invalid, in which case proceed with the old target.
      $destination = $request->query->get('destination');
      if ($destination) {
        // The 'Location' HTTP header must always be absolute.
        $destination = $this->getDestinationAsAbsoluteUrl($destination, $request->getSchemeAndHttpHost());
        try {
          $response->setTargetUrl($destination);
        }
        catch (\InvalidArgumentException $e) {
        }
      }

I've simply removed destination query parameter from request. I think this won't have any undesirable consequences (in cases where destination query parameter is actually desired). If later will be the case we can make it a bit more complicated and just add a lupus_ce_renderer_redirect attribute to request and then write a service decorator for RedirectResponseSubscriber that has another condition before applying the destination query parameter override.

For now this solution works:

<base-url>/ce-api/node/add/article?destination=bar => "<base-url>/node/add/article?destination=bar"

Works on our ci environments and no regressions were recorded, Thus merging.