Refactoring + Unit tests

[shenanigans-be]

We're finally professionalizing up in here, because my I-threw-this-over-the-weekend style of architecture is causing problems. 🫠

This started as a pretty innocent attempt to introduce Unit testing into the project, but soon grew into a full refactor of pretty much the entire back-end.
I realised that in order to do Unit testing, we need units, and the classes and implementations now were way to huge to be tested effectively.

This refactor aims to fix the following things:

• Break functionality up into smaller components.
• Work with typed values where possible.
• Implement unit tests on every level
• Run the unit tests in github actions for every PR so I don't have to manually check every new feature (-> this is what started the whole thing)

[shenanigans-be]

Currently betatesting, courtesy of the fine TI community on reddit.
Feedback:

1. TE factions in the Advanced settings should be above the DS ones.
2. Show backend errors in the frontend (for validation or impossible slices)
3. Map generation seems to be different:

I rerolled the draft a couple of times and I noticed way less anomalies right in the middle of the slice, way more systems with planets adjacent to the HS and way less systems with planets adjacent to Mecatol Rex.

Almost all slices i generated had planets in all three systems adjecent to HS. Also felt like there were less difference between slices then before

I noticed this too. Lots more obstacles next to Mecatol, too

4. On moblie, when the admin passkey appears. It is too wide for me to see everything clearly
5. when I set minimum legendaries to 6 (shooting for one per slice) it would infinitely load
6. I don’t seem to be able to generate a draft on a mobile browser (chrome and safari) even after clearing
7. when you click on the systems of each slice on phone, the ones on the sides get their values partly hidden