Feedback microservice

[CommanderStorm]

This PR seperates feedback from our main API server.

Reasoning:

• it has virtually no shared dependencies (natural fault line)
• this way, we can deploy the feedback-API independently of the main server (both in time, scaling and reliability)
• security: this way, we can increase our isolation

Hidden reasoning: this makes building additional feedback-features (e.g opening a PR on coordinate feedback 😉) less cluttered and better reviewable

[octycs]

I'm sorry that I've been quite inactive recently; I will try to give feedback until the end of the week.

[CommanderStorm]

I'm sorry that I've been quite inactive recently

No worries:
None of the ready for review commits (#293, #282, #257, #325) are on any sort of timeline nor are urgent in any way.
None of these changes are application breaking features or improvements.
This is a marathon, not a sprint.

The only one of our PRs being a big deal is #317 and that one will only be reviewed on docs. (this will unblock #200 and make reviewing that one possible…)

[octycs]

Looks good! I only noticed that Firefox blocks Port 6000 for security reasons (See this old documentation). So maybe a different Port would be better.

[CommanderStorm]

Interesting, I did not notice this, as I don't test the APIs not in the browser.