Make Project and TaskType names unique by Organization

[fm3]

Project and TaskType names had to be globally unique. Now, they are uniqe per organization.

TODO

• change unique constraints in schema
• add organization during insert
• change project api (by orga+name/by id/by disambiguation)?
• change edit view route
• use new api in frontend
• adapt task search form
• task search form persistence? → follow-up Double-Check that localstorage persistence typechecks work #5337
• how to access project name for rendering form?
• adapt access queries
• rest api versioning
• evolutions
• snapshot tests

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• List projects, create project, edit project, should all still work as expected
• Create tasks, search for tasks by project, should show.
• Try to create second project with the same name, should fail with readable message.
• Create second organization
• Create project with name used in other org, should work
• Edit projects, the ones across organizations should not influence each other
• same with task types.

Issues:

• fixes Project/Task type names names should not have to be unique across all organizations #4005

---

• Updated (unreleased) changelog
• Updated (unreleased) migration guide if applicable
• Updated documentation if applicable
• Ready for review

[philippotto]

Great work! The front-end changes look very good 👍 Let's wait for the back-end review.

[youri-k]

The code LGTM. See my minor question.

The other thing that should be checked is if we need all the indices in the db because AFAIK postgresql automatically creates indices for unique constraints, e.g. https://github.com/scalableminds/webknossos/blob/project-tasktype-unique-by-orga/tools/postgres/schema.sql#L432