Lab Report - HTTP 400 fix

[mpeels]

Description

During my investigation into the http 400 status errors observed when manually creating a Lab Report, I implemented a quick fix and wanted to push this up as a starting point since it appears to resolve the issue locally. Its possible we might also just be able to use a URLEncoder to encode the URL, but I am concerned that this will lead to a "double encoding" as some characters are already encoded by NBS 6.

Tickets

NBS-Central-18504

Checklist before requesting a review

• PR focuses on a single story
• Code has been fully tested to meet acceptance criteria
• PR is reasonably small and reviewable (Generally less than 10 files and 500 changed lines)
• All new functions/classes/components reasonably small
• Functions/classes/components focused on one responsibility
• Code easy to understand and modify (clarity over concise/clever)
• PRs containing TypeScript follow the Do's and Don'ts
• PR does not contain hardcoded values (Uses constants)
• All code is covered by unit or feature tests

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud