Describe the bug

When configuring RabbitMQ behind Authentik as a proxy provider, accessing a queue in RabbitMQ provides a link such as:
https://app-url/api/queues/%2F/MYChannelCreated?lengths_age=60&lengths_incr=5&msg_rates_age=60&msg_rates_incr=5&data_rates_age=60&data_rates_incr=5
However, Authentik responds with a 301 redirect, removing the "%2F". The new location provided is /api/queues/MYChannelCreated?lengths_age=60&lengths_incr=5&msg_rates_age=60&msg_rates_incr=5&data_rates_age=60&data_rates_incr=5, which results in a 404 error for RabbitMQ as it does not recognize this path.

To Reproduce
Steps to reproduce the behavior:

1. Configure RabbitMQ behind Authentik as a proxy provider.
2. Access a queue in RabbitMQ.
3. Observe the link provided and the resulting 301 redirect from Authentik.
4. Notice the 404 error due to the modified path.

Expected behavior
The expected behavior is that Authentik should maintain the "%2F" in the redirect link, allowing RabbitMQ to correctly recognize and access the specified queue.

Version and Deployment (please complete the following information):

• authentik version: 2024.12.1
• Deployment: docker-compose

Additional context
This issue has been previously raised but remains unresolved and closed automatically due to inactivity, as seen in this issue. #7172