Handle Sass parse errors

[notlee]

Relates to: https://sentry.io/organizations/nextftcom/issues/1135337606/?environment=prod&project=1296601

Sassdoc generation for o-normalise@1.3.0 fails as it has a missing semicolon at the end of a file. This is apparently valid Sass and appears to be an issue with scss-comment-parser which sassdoc depends on.

It's not a big issue as the missing semicolon has been added in a patch release of o-normalise, but some users continue to try to access the Sassdoc for the previous version.

I don't think we can catch and handle similar rare cases as the error is thrown within a sassdoc stream we don't have access to (unless we use node's deprecated domain maybe?) I've opened an issue against sassdoc with proposed solution.

[notlee]

The PR was released in sassdoc@2.7.1 🎉 configured Renovate and going to let that open the PR for us

[notlee]

#28