Object storage

Object storage support has been widely requested ( and is something we're keen to support. The limitations imposed by object storage happen to be beneficial for data resilience and consistency, as it makes features like the storage template infeasible. Issues like orphaned assets (#2877) or asset availability (#4442) would be resolved completely. As discussed on the orphaned assets issue (#2877), I'd like to propose a new storage layout designed for object storage, with scalability and resilience as priorities. Where: • <asset id> is a unique ID for an asset, ideally a random UUID. [UUIDv7]( may serve to be beneficial due to its property of natural order. If not, UUIDv4 should be sufficient. • <original asset filename> is the original filename of an asset, as it was uploaded. The above structure should serve to efficiently scale with resiliency and flexibility. The unique 'directory' for an asset can contain additional files …