Splitting application and platform code about stamhoofd

[SimonBackx]

Personaly I think we need to go for your first strategy, but maybe a more hybrid approach. Splitting the platform features and having to run a separate process for each organization makes it a lot harder and inefficient to scale the platform itself, which is also a requirement. I also think the dead code will be very limited, and doesn't have any negative impact apart from the idea itself (as you don't need to load dead code in the frontend and it doesn't really matter in the backend).

Currently we can still improve on separating organization specific logic, but it is split quite good already, e.g. each organization has its own API domain and associated endpoints. But still some development work is required to lock a local installation to a single organization. We also should consider splitting the organization selector / sign up from the dashboard itself in the future, and this could be replaceable with an installation system for a single installation (locking signing up a new organization as soon as the installation is complete).