terror: provide a RegisterFinish API

[tiancaiamao]

What problem does this PR solve?

Prevent regression like pingcap/tidb#28190

What is changed and how it works?

TiDB will register all the error kinds in its initialization, and then call this API
After that, misuse of the terror will panic, thus the bug is exposed early.

Check List

Tests

• Manual test (add detailed scripts or steps below)

In TiDB

Code changes

• Has exported function/method change

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• ichn-hu
• kennytm

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[tiancaiamao]

pingcap/tidb#28438

[ichn-hu]

LGTM

[tiancaiamao]

My main point is actually here pingcap/tidb#25405 (comment)

Is there some way to prevent this kind of error in the future?
Maybe nobody read the document and maybe people still make this kind of mistakes in the future.

We have got stuck on the error before, and fixed it then.
But later a contributor file a PR and misuse the terror package again...
This time we're not so lucky, the reviewers don't catch it and our customer trigger the bug

[tangenta]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: bd914f4