Delete bors.toml in favor of GitHub merge queues

[frewsxcv]

• I agree to follow the project's code of conduct.
• I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

---

[michaelkirk]

I clicked "merge when ready".

goodbye bors. You were a good bot. 😢

[michaelkirk]

Hmmm.

After merging this, I just queued #167 for merge. It seems to have immediately merged without running any tests and now main is red.

3fed23a

I guess I had the wrong idea about merge queues. Do you understand how to get a bors like workflow, where the branch is synced with master and tests are run before merging?

Also - did you intentionally choose to squash commits from the merge queue @frewsxcv? I know there are different schools of thought on this, but I like to be able to have multiple commits when it makes more sense, and I can pre-squash only when it makes things clearer.

[urschrei]

Oh yeah you need to modify the CI yaml (and enable branch protection? Not sure) I think. It's almost but not quite just flipping a switch. https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue