misc: run Lighthouse CI without assertions

[lex111]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

This should not prevent the creating of a comment with the report in case of insufficient score (see https://github.com/facebook/docusaurus/runs/6289742244?check_suite_focus=true)

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	72fee14
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/627275048ea72d000a429b65
😎 Deploy Preview	https://deploy-preview-7308--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[slorber]

just wondering if it's possible to fail the CI check and yet publish the comment?

It's a practice to turn assertion to 100% score and disable some rules, ensuring that we never regress from that point

[lex111]

just wondering if it's possible to fail the CI check and yet publish the comment?

Apparently yes, I was too hasty with this deletion, since I should better change error to warn, and CI check was passed without fail.