This is an automated cherry-pick of #5667

What problem does this PR solve?

This PR is addressing the issue issue-5657

Adding support for the logRestoreStartTs option in the PITR restore spec.

What is changed and how does it work?

With this update, the Point-in-Time Recovery (PITR) restore mode allows users to apply PITR logs within a specified time range. Specifically, users can define the start and end timestamps using the logRestoreStartTs(start timestamp) and pitrRestoredTs(end timestamp) options in the restore spec, respectively. This enhancement enables more precise control over the restoration process, allowing users to restore data to an exact point in time by specifying the interval of PITR logs to be applied.

After this change the user can use a combination of pitrFullBackupStorageProvider and pitrRestoredTs, to restore the full backup snapshot and apply PITR logs. or else a combination of the logRestoreStartTs and pitrRestoredTs options in the restore spec to apply PITR logs within a specified time.

If the user fails to specify either the pitrFullBackupStorageProvider or logRestoreStartTs option in the restore specification, the restore job will result in an error.

Code changes

[x] Has Go code change
[ ] Has CI related scripts change

Tests

[ ] Unit test
[ ] E2E test
[x] Manual test
PITR up to mentioned restoreTs along with full backup restore.
1. Create a TiDBCluster
2. Generate some data in the database (I used Sysbench prepare subcommand)
3. Start the PITR log Backup, refer Log Backup
4. Create a full backup, Full backup
5. Now create another TiDBCluster to test the backup restoration.
6. Follow the steps to restore full backup and apply PITR logs to the specified point(timestamp). refer Restore full backup + apply logs

Apply PITR logs within a specified time range.

Create a restore-pitr.yaml file as follows, then use kubectl apply to apply the yaml.

restore-pitr.yaml

 ---
 apiVersion: pingcap.com/v1alpha1
 kind: Restore
 metadata:
    name: demo3-restore-gcs
    namespace: restore-test
spec:
  restoreMode: pitr
 br:
     cluster: demo3
     clusterNamespace: test3
 gcs:
     projectId: ${project_id}
     secretName: gcs-secret
     bucket: my-bucket
     prefix: my-log-backup-folder-pitr
  logRestoreStartTs: "2022-10-10T16:21:00+08:00"
  pitrRestoredTs: "2022-10-10T17:21:00+08:00"

Side effects

[ ] Breaking backward compatibility: NONE
[ ] Other side effects: NONE

Related changes

[ ] Need to cherry-pick to the release branch
[x] Need to update the documentation

Release Notes

NONE

pingcap / tidb-operator

Adding support for logRestoreStartTs option in PITR restore spec (#5667) #5669