Login platform and SSO implementation

[this-pama]

This PR introduces a significant update to our authentication system. A new login platform will be created to handle all login-related actions. Additionally, configurable system variables have been set for restricted and allowed desired route paths, tailored to different platform instances. This has no impact on existing instances, but will be needed for the login app as some routes are restricted within the application. Going forward, we can use these variables to configure restricted or allowed paths within the platforms. Additionally, the required setting up for SSO (Single Sign-On) integration logic have also been implemented. Once we have the the required token from the responsible teams, we can enable the SSO functionality. The SSO button can be disable from the configuration file until we are set and ready to open this to the user.

Requirements for this PR:

• Update users and trusted_devices table.
• Add CLIENT_ID, TENANT_ID and CLIENT_SECRET to environment variables. These variables are needed for the organization sso configuration. You may set these to empty string for now.
• Create new domain login.sdg...org
• Create new platform instance for login. The APP_ID is login and the config file is login.js.
• Once we are ready to open-up the org sso login, we can update the CLIENT_ID, TENANT_ID and CLIENT_SECRET variables and make the SSO login button accessible by setting the value to true in the index.js config file.

[this-pama]

TODO:

Add a middleware to block all routes except the login for login platform (done) Create contributors only from login platform (done) Check whether removing pads from the config module breaks system. (No impact on system. however pad menu is still showing even when not enabled in the configuration file) Have a button to request elevated rights from the login platform. ( What happens when a user request elevated rights? Who can approve a request for rights elevation? Any users with rights 3 and above or the collaborators? who gets notified when a user request elevation? e.t.c. User flow for requesting elevated rights need to be discussed.