refactor/review multitenancy system implementation from the frontend perspective

[Baalmart]

Is your feature request related to a problem? Please describe.
First time users were not able to easily access the system. As described in the attached screenshot. For first time users, that organization is very confusing.

Afterwards, this was addressed by removing the org field and handling it from the backend. Default cases are airqo and other orgs require one to add a path in the url, example: /kcca as shown below

Describe the solution you'd like
Still handling the tenancy without requiring additional user actions when visiting pages.

Describe alternatives you've considered

• Add airqo as the first path before other the urls, example: https://platform.airqo.net/airqo/login instead of current one which is: https://platform.airqo.net/login/kcca so that is visible.
• Using subdomains.

Additional context
Picked from a service desk issue. The proposed solutions could also be related to this open API-PR-575

[123MwanjeMike]

More alternatives to consider

1. User selecting organisation from list of curated organisations on sign-in form.
2. Deriving user's organisation from login email domain.
3. Using shared database for login, back-end then determines which organisation user belongs to.
4. Using a shared database for all tenant data

[123MwanjeMike]

Intresting insights to pick from this article in relation to this issue