feat: support redis(standalone replica) pitr

[Chiwency]

Resolves #7999

We leverage the AOF backup feature from Redis version 7.0 onwards to implement Point-In-Time Recovery (PITR). By enabling the aof-timestamp-enabled yes and aof-disable-auto-gc no parameters, we activate AOF timestamp annotations while disabling the automatic cleanup of historical AOF files. A StatefulSet, which is continuously responsible for the ongoing backup process, manages and tracks the AOF files.

The continuous backup process works as follows:

1. Historical AOF files in the data directory are compressed, packaged, and pushed to the backup repository.
2. The latest AOF file is backed up to the repository directory and continuously updated. When Redis triggers AOF rewriting, the file is compressed and archived as described in step 1.
3. The backup files in the repository are named using the format ${base_file_ctime}.${seq}.${suffix}, where base_file_ctime is the creation time of the base aof file, marking the start of this particular backup package. This timestamp creates a continuous timeline for all backups. The seq is a sequence number used for recovery in case of a backup pod failure.

The recovery process works as follows:

1. Based on DP_RESTORE_TIME, the backup package with the base_file_ctime closest to DP_RESTORE_TIME is selected. This base file's data is used as the starting point. Then, AOF files are processed according to their timestamp annotations , up until DP_RESTORE_TIME is reached.

[ldming]

@Chiwency It would be helpful to explain your implementation approach in the PR description so that everyone can understand it.

[Chiwency]

@Chiwency It would be helpful to explain your implementation approach in the PR description so that everyone can understand it.
done

[ldming]

The addon PR is apecloud/kubeblocks-addons#961