docs: Fix links in README!

[JohnMcLear]

Just some README polish to fix broken links..

[qodo-code-review]

ⓘ You've reached your Qodo monthly free-tier limit. Reviews pause until next month — upgrade your plan to continue now, or link your paid account if you already have one.

[qodo-free-for-open-source-projects]

Review Summary by Qodo

Fix broken links and update badges in README

📝 Documentation

Walkthroughs

Description

• Remove outdated Sauce Labs badge references
• Simplify frontend test badge labels
• Fix broken Etherpad plugins link to correct URL
• Remove Windows Build badge from status section

Diagram

flowchart LR
  A["README.md badges section"] -->|Remove Sauce Labs refs| B["Simplified badges"]
  A -->|Update plugin link| C["Correct plugin URL"]
  B --> D["Cleaner status display"]
  C --> D

Loading

File Changes

1. README.md 📝 Documentation +3/-5

Update badges and fix plugin documentation link

• Removed "powered by Sauce Labs" text from frontend test badges
• Removed Sauce Test Status badge and Windows Build badge
• Updated Etherpad plugins badge link from https://static.etherpad.org/index.html to
 https://etherpad.org/plugins
• Simplified badge labels for better clarity

README.md

---

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1)

1. Explicit protocol in README URL 📘 Rule violation ⚙ Maintainability

Description

The newly added README link uses an explicit https:// URL, but the style rule requires
protocol-independent URLs (//...) where applicable. This can cause inconsistent URL style and
potential issues when rendered under different schemes.

Code

README.md[46]

+[![Etherpad plugins](https://img.shields.io/endpoint?url=https%3A%2F%2Fstatic.etherpad.org%2Fshields.json&color=%2344b492 "Etherpad plugins")](https://etherpad.org/plugins)

Evidence

PR Compliance ID 7 requires protocol-independent URLs (//...) where URLs are used in that context.
The added line in README.md includes explicit https:// URLs (both the badge image and the link
target).

README.md[46-46]
Best Practice: Repository guidelines

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A newly added README link uses an explicit protocol (`https://`) but the style requirement calls for protocol-independent URLs (`//...`) where appropriate.

## Issue Context
This PR modifies `README.md` and introduces/keeps explicit-protocol URLs on the changed line.

## Fix Focus Areas
- README.md[46-46]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---