Files table and management system

[davenquinn]

This system should be based around a files or objects table and should allow:

• Linking to files stored in S3 buckets (either under our control or managed externally)
• Tracking of basic bucket/file metadata (e.g., hashes, access dates, content types) so we don't have to grab it from AWS each time

• Support eventual development of a basic suite of tools for file hygiene: checking/removing/verifying access etc.

  This will be critical for all manner of ingestion and file management tasks.

Prior art:

• This storage system schema I implemented based on Supabase's design.
• Supabase storage system.

While Supabase's API isn't exactly what we want, I think (it assumes storage in a single S3 bucket and is generally quite tailored to their use case) maintaining alignment and potentially compatibility would be useful.

[davenquinn]

Starting to work on this in #13 !

[davenquinn]

@brianaydemir @CannonLock , it sounds like this is being worked on — is there a stable pull request that can be separated from the rest of the additions for your user interface? Or is the schema somewhere else?