Rework project structure and clarify the collection concept

[annavik]

At the moment, project settings are a bit confusing. Project names and cover images are edited from the gallery view, while project entities (like pipelines, storage, sites, etc.) are edited from the project summary view. Also, we should try clarify the collection concept. This seems to be a bit unclear to users.

In this issue we capture some ideas from chats between @annavik and @mihow. We need to be split this issue up into more concrete sub tasks before implementation.

Thoughts:

• Can we have one united place for all project settings?
• Should collections be extracted from the project settings? Could be a main menu item?
• Rename collections to "Datasets"?
• Do we really need the "Session" concept? Could be a "per night" dataset?
• It would be cool if we could use our current playback view to navigate captures from datasets. At the moment, we can only do this for one session.
• One view for showing all captures? With filtering.
• New main menu structure?
  • Overview
  • Stations
  • Captures
  • Datasets
  • Occurrences
  • Taxa

[annavik]

@mihow feel free to update/add based on your notes! :)

[annavik]

Notes after meeting 11/2
I will try split this issue up, this one is very big and also quite vague. @f-PLT will also start dig into this a bit.

Suggestion:

• One task for updated project settings
• One task for making project entities part of project settings
• One task for changes related to captures/collections/sessions

The only task I see as being related to the milestone "permissions and private projects" would be the first one in this list. The last task in the list I expect to be the largest one. If we will go as far as replacing sessions with collections, I expect it to also include major backend changes.

TBC!