fix: 227/support pre-encoded urls

[toby-farris-bd]

Create a new config option to allow consumers to "inform" rascal about the url configured, specifically which parts of it are pre-encoded.

Description

the PR is small enough to understand, I think

Related Issue

227

Motivation and Context

see issue

How Has This Been Tested?

If you like this approach, I'll look into how to write a unit test. I've tested it from my fork in my working project.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[cressie176]

Hi @toby-farris-bd,
I think it's simpler just to decode the components parsed by new URL(). I created a PR to test