fix(prerender): allow spaces in href value regex

[juliesaia]

🔗 Linked issue

#1029

❓ 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)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Removes the space character from the end group character set in LINK_REGEX. Only single/double quotes can end the match now, allowing for href paths with spaces in them.

Resolves #1029

📝 Checklist

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

[pi0]

LGTM. BTW space is not normally an allowed char (#1029 (comment))

[TheAlexLichter]

Should we emit a warning in this case (and allow it)?

[codecov]

Codecov Report

Merging #1030 (701dbb7) into main (b495675) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1030      +/-   ##
==========================================
- Coverage   67.59%   67.51%   -0.08%     
==========================================
  Files          62       62              
  Lines        6259     6259              
  Branches      707      706       -1     
==========================================
- Hits         4231     4226       -5     
- Misses       2015     2019       +4     
- Partials       13       14       +1     

Impacted Files	Coverage Δ
src/prerender.ts	89.34% <100.00%> (ø)
src/presets/cloudflare-pages.ts	85.26% <0.00%> (-1.06%)	⬇️
src/rollup/config.ts	87.55% <0.00%> (-0.88%)	⬇️

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

[pi0]

Should we emit a warning in this case (and allow it)?

We might do it in higher order (prerenderer) with an opt-in validate feature. Seems browsers can handle it at least apart of the spec.