Overhaul buildbot worker setup documentation

[stratakis]

As I've recently had to setup again the aarch64 buildbots, I've taken a shot at re-reading and verifying the current docs. I've rewriten the Linux buildbot worker setup instructions with per-distro nested tabs, all of which I've verified in containers and VMs.

Also added recommended buildbot.tac settings, FreeBSD rc.d instructions, and pip/manual setup for distros without available buildbot packages.

Plus some minor MacOS fixups.

[read-the-docs-community]

Documentation build overview

📚 CPython devguide | 🛠️ Build #31747943 | 📁 Comparing 7c721c2 against latest (5a4dd49)

🔍 Preview build

Show files changed (4 files in total): 📝 4 modified | ➕ 0 added | ➖ 0 deleted

File	Status
testing/index.html	📝 modified
versions/index.html	📝 modified
developer-workflow/psrt/index.html	📝 modified
testing/new-buildbot-worker/index.html	📝 modified

[stratakis]

Also another section that I believe warrants an update is the "Required resources" one as it still references a 2012 survey recommending e.g. 512 MB RAM. This is likely too low for modern CPython builds. python/cpython#133454 shows some tests now consume >1 gb, and github actions CI runners use 16 gb. However I don't have data on possible minimal specs, so I left it untouched, but maybe some higher baseline would be better.

[hugovk]

By the way, cstratak-fedora-stable-ppc64le is now failing with timeouts: https://buildbot.python.org/#/builders/435

• last pass: https://buildbot.python.org/#/builders/435/builds/6753
• first fail: https://buildbot.python.org/#/builders/435/builds/6754

[stratakis]

By the way, cstratak-fedora-stable-ppc64le is now failing with timeouts: https://buildbot.python.org/#/builders/435

* last pass: https://buildbot.python.org/#/builders/435/builds/6753

* first fail: https://buildbot.python.org/#/builders/435/builds/6754

I believe this is due to llvm/llvm-project#179695, we'll need to have clang fix it.

[stratakis]

@encukou btw should I follow the CPython conventions here for the PR? Aka every next fix to get its own commit and not rebase? Is everything squashed before a merge here?

[StanFromIreland]

Is everything squashed before a merge here?

Yes, please don't force push.

[encukou]

Everything's squashed.
Don't force push (so we don't need to re-review everything). And don't worry about rebasing before a push -- neatly split commits are only nice-to-have.