Make Project and TaskType names unique by Organization (second try)

[fm3]

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

Reverts #5379 (which reverted the original #5334 )

Difference being that the unique constraint is no longer enforced in the database, but only via scala, compare issue description in #5388 I also made sure that the name is immutable (front-end already grayed out the form value, but backend didn’t enforce it) See last commits for the diff.

Quoted from original PR:

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

[youri-k]

LGTM