Add README sponsors

[cjbarth]

Add some more badges and sponsors to the README file

Summary by CodeRabbit

• Documentation
  • Updated build status and code-quality badges at the top of the README for clearer project status.
  • Added a Sponsors section showcasing sponsor logos with links.
  • Replaced legacy blog/twitter badge block and removed outdated badges, and renamed/reorganized related sections for clearer README structure.

[coderabbitai]

Walkthrough

The README.md is updated: build badges replaced with new Build Status and code quality badges, a Sponsors section with logo links was added, the Bitdeli badge was removed, and prior blog/twitter link blocks were replaced by sponsor entries.

Changes

Cohort / File(s)	Summary
Documentation Updates README.md	Replaced older build badges with new Build Status and additional code quality badges; added a Sponsors section with sponsor logos and links; removed the Bitdeli badge; replaced blog/twitter link block with sponsor logo/link entries.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 A README polished, badges bright as day,
Sponsors nestled where the links once lay.
I hop with joy, a tiny, thankful chap—
New logos gleam upon the map. ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Add README sponsors" is clear, concise, and directly related to a significant change in the PR. The changeset primarily adds a new Sponsors section with sponsor logos and links to the README, which the title accurately captures. While the PR also includes badge updates and section restructuring, the instructions acknowledge that titles don't need to cover every detail of the changeset. The title effectively communicates the main feature addition from the developer's perspective and uses specific, descriptive language rather than generic terms.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 84677ae and 67b6315.

📒 Files selected for processing (1)

• README.md (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ff1f58a and 84677ae.

📒 Files selected for processing (1)

• README.md (2 hunks)