* ci: SonarCloud analysis from CI instead of automatic analysis
* Publish the worker's node:test coverage to SonarCloud (test:coverage)
* ci: shared SonarCloud workflow back on @main (node coverage merged in craft-common-actions#194)
Chrome warns because Safe Browsing lists some craft.wiki pages as phishing, and
the Worker's sign-in page was a bare "Craft Wiki sign-in" title served from an
/api/ path with no branding, no explanation and no security headers. Give it the
wiki's branding, say that the password prompt belongs to discord.com, and send a
CSP with framing, referrer and content-type headers.
Add a script and a daily workflow that report Google's verdict for the domain,
so a listing is noticed without waiting for a browser to show it.