Remove bors and use GitHub merge queue

[curquiza]

Ruleset set up for the usage of GitHub merge queue ✅

[coderabbitai]

Warning

Rate limit exceeded

@curquiza has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 20 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between d96d4aa and ffdc21b.

📒 Files selected for processing (5)

• .gitattributes (0 hunks)
• .github/release-draft-template.yml (0 hunks)
• .github/workflows/tests.yml (1 hunks)
• CONTRIBUTING.md (0 hunks)
• README.md (0 hunks)

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch remove-bors

---

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