feat: update tenant management RFC to include multipart uploads

[alanshaw]

📖 Preview

Summary

This PR just updates the existing RFC for tenant management to document the S3 permissions and Forge commands required to support multipart uploads.

[parkan]

as written this needs /blob/remove, or blobs need to be parked until Complete (conflicts with https://github.com/fil-one/RFC/pull/17/changes#diff-18ca746d83487824ea53f04b055a5ba3b0002c06c981c108aab5ac81b70efb92R232) in case of e.g. re-uploading, otherwise we need specific GC machinery with its own state

[parkan]

also for overwrites (S3 semantics require only s3:PutObject for that unless locked/versioned/etc) but we'd need to remove first

we could say we default to If-None-Match and 412/409 but this needs to be explicit

generally speaking not requiring /blob/remove as baseline for uploads seems good but as currently specified I see at least two cases where this isn't conformant

[alanshaw]

❤️ thank you - we also realised this and addressed in fil-forge/hilt#37

I'll update here also.

[bajtos]

Why do these two S3 permissions need /blob/abort? Any why they don't need /blob/remove similarly to s3:PutObject?

[alanshaw]

Good point. I don't think they need /blob/abort...they don't need /blob/remove because IIRC it is writing local state, not actually writing to the Forge network (which is always a remove then add operation when updating due to immutable data).