per space properties #2259
Description
Currently, all spaces managed by a storage provider follow the same configuration. However, requirements for spaces vary. A space used for e.g. Joplin does not need to fill the activity log. Files are named by their uuid anyway. Versioning can be disabled, because Joplin keeps track of the history itself. Finally, Etag propagation and size tree accounting are not needed, because Joplin uses its own sync algorithm: all notes are stored in a flat list and the mtime is used to detect changes. Even Trash support is optional ... and event async postprocessing is not needed (it might actually be a problem for clients not supporting our 425 status code)
Then there are issues that may require us to change the xattr keys, eg. because SMB does not allow : in keys or because spaces in posixfs are stored on different filesystems
Finally, there might be archived spaces that are read only or updated by external mechanisms or tools that do not necessarily support change notifications. One example would be a read only space that will never change, another would be an s3 bucket that is managed by another application but end users still want to be able to browse the files. For the latter a periodic sync could be set up that only crawls the tree every sunday. This would be the update frequency: notifications, sync every 7d or on browse... or a combination of those ... something end users can understand.
We already have a space.json ... maybe use it to allow end users to configure the space? and have an additional config file that only admins can edit?
cc @aduffeck @rhafer @dragonchaser Since we keep returning to this idea I wrote it down. Now we can reference existing issues if they are related...