feat(publisher): add clear rate limit for tiup publishing

[wuhuizuo]

Signed-off-by: wuhuizuo [email protected]

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

The pull request title indicates that the changes found within are related to the addition of a clear rate limit for tiup publishing.

Here are the key changes in the pull request:

1. A new endpoint reset-rate-limit is added to the service "tiup". This endpoint allows for rate limit reset functionality.
2. The new endpoint is registered in the client and server files for the "tiup" service.
3. A new handler for the reset-rate-limit endpoint is added.
4. A new function ResetRateLimit is added to the tiup service interface and its implementation.
5. A rate limit key is added in the rate limit check function.
6. The openAPI files are updated to include the new endpoint.

Potential problems:

1. There is no clear indication of what the rate limit actually is. If the rate limit is too low, it may hinder usage of the service. If it's too high, it may not protect the service effectively.
2. There is no authentication or authorization in place for the rate limit reset endpoint. This could lead to abuse of the system.
3. The rate limit resetting is done by deleting keys from Redis. This could potentially cause issues if other data is being stored in Redis under similar keys.
4. There are no tests included with these changes. Without tests, it's hard to ensure that the new functionality is working as expected.

Suggestions to fix the problems:

1. The rate limit should be clearly defined somewhere, either in the code or in documentation.
2. Implement some form of authentication or authorization for the reset-rate-limit endpoint to prevent unauthorized access.
3. Consider namespacing or otherwise differentiating the keys used for rate limiting to avoid conflicts.
4. Add tests to cover the new functionality and any related functions to ensure everything is working as expected.

[wuhuizuo]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [wuhuizuo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment