Ask for extending default expiration date for initialized empty TiUP repo and supporting renewing after expiration

[haiboumich]

Feature Request

Is your feature request related to a problem? Please describe:

I have built a TiUP repo from scratch using tiup mirror init and found that it would expire after one month, which is not an expected result for our project. Using tiup mirror merge <mirror> would update the expiration time but it would still be one month from the merging moment.

Another problem we encountered is that once the repo is expired, we would not have a chance to renew the expiration date through the command tiup mirror renew <component>.

Describe the feature you'd like:

Corresponding to the problems described above, I am wondering if the expiration date for the repo built by tiup mirror init could be longer, i.e., I have checked that the expiration date in the TiDB community server installation package(https://download.pingcap.org/tidb-community-server-v5.2.2-linux-amd64.tar.gz) is 2071-10-17T06:35:50Z.

Also, it would be better if we are able to recover an expired repo by tiup mirror renew.

Why the featue is needed:

The scenario would be like this:

1. build an empty repo from scratch using tiup mirror init
2. initialize the repo by publishing some project perspective components into it using tiup mirror publish
3. put a TiDB community server installation package like tidb-community-server-v5.2.2-linux-amd64.tar.gz into the repo by tiup mirror merge, which will be used to deploy v5.2.2 TiDB clusters.
4. once a new TiDB version is released, maybe some months later, we may want to merge the new package into the repo to deploy the new version TiDB clusters.

Clearly, we encountered the problem in step 4.

Describe alternatives you've considered:

I do not have alternatives for now.

Teachability, Documentation, Adoption, Migration Strategy:

N/A