Collect requirements for replication: on what basis will we do it, how often to upload/download, move to other buckets

Ref: https://0chain.slack.com/archives/C06K3JX7WG4/p1708370353197439

We want to replicate to archive so that we can use it for recovery on S3 if needed.
We want to offer our customers S3 and Archive solutions with [zero RPO and RTO disaster recovery](https://medium.com/@bijit211987/approaching-zero-rto-rpo-architectural-considerations-and-best-practices-3848e7252894#:~:text=Zero%20RTO%20aims%20to%20eliminate,failover%20mechanisms%20to%20minimize%20RTO.).

From our perspective, S3 and Archive are just different h/w and b/w but same type of allocation but over different sets of servers.

The issue references a Slack discussion about replicating data to an archive for disaster recovery with zero RPO/RTO. Start by examining the existing allocation and storage layer code to understand how data is currently stored and managed. Look for any existing replication logic or S3/archive integration points. The goal is to define requirements, not implement a solution, so focus on understanding the system architecture and documenting the replication strategy.

Written by the indexing model from the issue text.