We need more contributors

### Prerequisites

- [x] I have read [CONTRIBUTING.md](https://github.com/EFForg/rayhunter/blob/main/CONTRIBUTING.md)

### Bug Report Details

Rayhunter is gaining popularity, and many issues are left to be fixed. Support
volume is growing but our bus factor stays about the same. Maintainers are
stretched thin across other projects. We need more contributors.

Here is the help we need right now:

* We need more people to improve documentation. Some things are still phrased confusingly, or are out of date. This outdated information is then repeated elsewhere.
* We need more people to investigate bugs instead of developing features. Installation still sometimes fails, and it's not clear why. Usually a retry or buying another device fixes it.
* We need more people to give feedback on the development process, which means everything from collaborating in the issue tracker to setting up the devenv to writing code. Please do that in this thread.
* We need improvements to the development environment itself. I have started here: https://github.com/EFForg/rayhunter/pull/851 but ideally that document should have fewer steps to begin with.
* We need fewer vibecoders. I find that in the past few days there have been many well-meaning attempts to contribute to Rayhunter without having expertise in Rust and letting AI do most of the work. This leads to situations where the initial code looks like progress, but the review process takes way too much time to be effective. This is not to say that you shouldn't use AI at all, but ultimately you have to understand and review what you're submitting. See also https://github.com/EFForg/rayhunter/discussions/867
* **We need documentation on how to run rayhunter on unsupported devices.** We are unlikely to add support for new devices in the installer officially (since it comes with expectations of support and maintenance), but at the same time people want to run Rayhunter on whatever device they have laying around. I am also however afraid that this will generate additional support volume for us, so we need to be careful about setting expectations.
* **We need recurring contributors.** There is no commitment to maintain something you're contributing to Rayhunter, but it would be nice. Especially as we gather more features we need people to maintain them.

Some of these things should probably be split out into separate issues, and added to CONTRIBUTING.md. For now I'll just pin it to gather feedback.