fix: respect encoded slashes in redirect header

[achmelo]

Description

Location header, in some cases, is being updated, and encoding is being lost. This change updates the header with respect to the original content of the header

Type of change

• fix: Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

[pavel-jares-bcm]

Maybe we could take care of AT-TLS. This solution doesn't help in using an outbound rule in a service calling the Gateway.

[pablocarle]

I understand it's covered in integration tests, but from a developer experience point of view, I find it not optimal that we need to verify the behaviour with integration tests. I'd expect that unit tests should cover these changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
84.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud