fix: sanitize statusMessage of disallowed chars

[danielroe]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

It will break the response if we set any of these characters by accident (e.g. if a user includes in an error message).

Related: nuxt/nuxt#14688

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codecov]

Codecov Report

Merging #357 (6ef3696) into main (a5e9fcd) will decrease coverage by 0.36%.
The diff coverage is 44.44%.

❗ Current head 6ef3696 differs from pull request most recent head 7117b79. Consider uploading reports for the commit 7117b79 to get more accurate results

@@            Coverage Diff             @@
##             main     #357      +/-   ##
==========================================
- Coverage   74.61%   74.25%   -0.36%     
==========================================
  Files          25       25              
  Lines        2336     2362      +26     
  Branches      368      368              
==========================================
+ Hits         1743     1754      +11     
- Misses        593      608      +15     

Impacted Files	Coverage Δ
src/utils/request.ts	85.04% <28.57%> (-13.80%)	⬇️
src/error.ts	77.35% <100.00%> (+0.73%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[pi0]

Just to mention for future we might extend the scaped for XSS as well (we had report of similar issues with ipx fixed by JSON.stringify and removing more chars)

[pi0]

Thanks ❤️