WIP: make organization name its id, drop the mongo id

[fm3]

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• abc

TODOs:

• update in sql schema
• update in scala code
• the mongoid is used as key in loki?
• update in routes
• update in proto
• update in frontend
• checks on name in sql and create organization code (allow [A-Za-z0-9\-_. ]+ in sql)
• test around
• sql migration, careful with foreign keys
  • to make rollback easier, keep old ids, rename to nullable unused column?
  • migrate analytics events json in postgres
    • for foreign-webknossos analytics events it may be that the id cannot be looked up. talk to norman on how to handle these.
• make sure that analytics events those from old webknossoses can still be ingested
• bump api version, provide adapters → only for routes used by python client. e.g. dataset_list
• todos in code
• change worker job arguments from organization_name to organization_id (maybe follow-up for easier rollbacks of this pr)
• ?

Issues:

• fixes Make the organization name its id, drop the mongo id #7689

---

(Please delete unneeded items, merge only when none are left open)

• Updated changelog
• Updated migration guide if applicable
• Updated documentation if applicable
• Adapted wk-libs python client if relevant API parts change
• Removed dev-only changes like prints and application.conf edits
• Considered common edge cases
• Needs datastore update after deployment

[MichaelBuessemeyer]

Notes for me:

still needs to be renamed to display name

and keep old _id column somehow for potential rollbacks