Fix URL signing api for URLs containing special characters

[ErykKul]

What this PR does / why we need it:
Bug fix; URL signing for URLs containing special characters broken in 6.10, this PR fixes the introduced bug.

Which issue(s) this PR closes:
Issue not created, bug fixed directly here.

Special notes for your reviewer:
Added tests to prevent regression. Also, API requires now the signing secret to be set, otherwise it will not work.

Suggestions on how to test this:
No special testing needed, the unit tests should be sufficient.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No

Is there a release notes update needed for this change?:
Yes, included.

Additional documentation:
No

[coveralls]

Coverage is 25.061% — fix-url-signing-special-characters into develop. No base build found for develop.

[github-actions]

Test Results

404 tests   389 ✅  32m 52s ⏱️
 55 suites   15 💤
 55 files      0 ❌

Results for commit 4fef358.

♻️ This comment has been updated with latest results.

[ErykKul]

@qqmyers Heads up before QA: a few more commits landed since my comments above. While testing against a real client I also made validation verbatim-first — the signature is checked against the raw request URI first, with the URL-decoded check kept as fallback — so a URL signed exactly as it will be used now works as received, and everything that validated before still validates. A final review pass added a couple of fixes on top: crafted user=!... values get a proper 401 instead of a 500, and tool-manifest urlTemplates get reserved params stripped before signing again like 6.10 did (otherwise key={apiToken} in a template would sign the user's real API token into the URL). All with unit tests; docs and release note updated. That's everything from my side.

[qqmyers]

@ErykKul - can we coordinate in slack and discuss this PR?

[pdurbin]

@ErykKul just a reminder that we'd like your input and code freeze for 6.12 is next Thursday! 🥶

[pdurbin]

We think only @ErykKul is actively using this but we'd like to get it into 6.12.

[ErykKul]

@pdurbin I am on it. Trying to wrap it up. Not ready yet, I will try to have it ready by tomorrow evening.

[sonarqubecloud]

Quality Gate failed

Failed conditions
61.8% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:fix-url-signing-special-characters

ghcr.io/gdcc/configbaker:fix-url-signing-special-characters

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.