Backup metastore

[MarinPostma]

This PR implements the meta store backup and restore logic using a bottomless-enabled connection. I cleaned up the code a bit to to reuse WAL wrapper patterns by implementing WrapWal for Option<T>
and used that for ReplicationWal and the meta store connection.

Configuration for the meta store durability is passed at thanks to new cli arguments:

      --backup-meta-store
          Enable backup for the metadata store

      --meta-store-access-key-id <META_STORE_ACCESS_KEY_ID>
          S3 access key ID for the meta store backup

      --meta-store-secret-access-key <META_STORE_SECRET_ACCESS_KEY>
          S3 secret access key for the meta store backup

      --meta-store-region <META_STORE_REGION>
          S3 region for the metastore backup

      --meta-store-backup-id <META_STORE_BACKUP_ID>
          Id for the meta store backup

      --meta-store-bucket-name <META_STORE_BUCKET_NAME>
          S3 bucket name for the meta store backup

      --meta-store-backup-interval-s <META_STORE_BACKUP_INTERVAL_S>
          Interval at which to perform backups of the meta store

      --meta-store-bucket-endpoint <META_STORE_BUCKET_ENDPOINT>
          S3 endpoint for the meta store backups

[LucioFranco]

are we going to have issues with these not being forwarded to the inner wal impl?

[MarinPostma]

It's forwarded by default; notice how we are not implementing Wal but WrapWal now :) this is a convenient trait that helps compose WAL implementations. Upstream, I have stuff like:

        let wal_manager = Sqlite3WalManager::default()
            .wrap(TakeReaderWrapper(tmp.path().to_path_buf()))
            .wrap(ReplicationIndexInjectorWrapper);

so that it's super easy to only implement what you need for WAL implementation that wrap other WAL implementations

[LucioFranco]

😯

[LucioFranco]

I think you're still missing the instrument macro though I think we should add that.