Creation of Organizational Spaces and smaller Auth Issues

[iaktern]

Creation of Org Spaces:

• in the "My Spaces" view:
  • Delete the Button to create a "New Organization" Space
  • add a button in each Space row to "Leave" a Space. Show a popup before leaving "Attention: You are about to leave the Space "<Space-Name>". This cannot be undone, except if someone within this Space adds you again."
  • show "My Personal Space" in the top row (also rename "My Space" to "My Personal Space" in the top drop down menu)
  • Add a settings gear symbol (<SettingOutlined />) to the "My Personal Space" row and also in the top right drop down menu. By clicking on it, it should open the settings view for the users personal space, which contains the same settings like organizational spaces have. (See Settings/Configurations of the MS and Spaces: Environment Variables, etc. #533 and https://github.com/PROCEED-Labs/proceed/wiki/MS-Configuration)
• In the Login Modal, add a tile to "Create a New Organization" (like with the new tiles for "Login by Mail" or "Login by Password"). During this, you should be able to create a new admin user or select your existing user account as admin (by login).

Other (Auth) Issues:

• Dev Mode: if starting the MS in dev mode and then login with "Try PROCEED" (guest mode), the Sign In seems to be the wrong one: it does not allow you anymore to login as dev user (admin or johndoe)
• Bug: the permissions inside a role look like they are turned off: if the switch is blue == true
• Update Available Roles/Permissions to existing Views
• delete old environment variables like PROCEED_PUBLIC_GENERAL_DEFAULT_CURRENCY that are not used anymore (see wiki)
• Change the default MS Administrator:
  • not the first logged-in user, but instead a predefined admin user called admin
  • realize the insertion of the admin-user with the seed file, which should then also be in the MS repo
  • admin password is always set in the seed file (default value), or optional inside an environment variable IAM_MS_ADMIN_DEFAULT_PASSWORD (useful for cloud deployment). this password can be changed at runtime. a restart of the MS should not reset the admin password then (even not if set via env variables).
  • username admin should not be changeable
  • default password: "proceed"
• if PROCEED_PUBLIC_IAM_ONLY_ONE_ORGANIZATIONAL_SPACE=true, then there should be no "Delete Organization" button
• "Create User" modal for creating new users: the X in the top right corner for closing the modal does not work
• Roles: no "expiration" -> what is it for? I assume, it is too advanced. I would remove it from PROCEED for now
• Login Mails: instead of Links, use numbers that you need to insert. This is way easier, because you can easily login at an untrusted pc and don't need to login into your mail account to get the link (reading the number on your phone is enough)
• Every User should have an option in his/her profile to create a random REST API token. the token needs to be used for accessing the REST API by adding it the header field Authorization: Bearer eyJhbGci.... Within the REST API, users should only be able to retrieve the data they have access to (spaces, processes, etc.)
• seed file extension for settings the ms admins
• seed file extension for showing the correct name in the sign-in dialog

...
  system: {
    name: 'Management System from PROCEED',
    description: 'This is the Management System from PROCEED.',
    msAdministrators: [
      'tds_admin', // This username has to match one defined in the users array
    ],
  },
...

• Seed file description in wiki with version and logo example