Add security configuration documentation and migrate security docs directory

[TopScrew]

First-time contributors' checklist

• I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added or deleted? (Required)

Add TiDB security configuration best practices and migrate security hardening docs directory

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

• master (the latest development version)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• v8.2 (TiDB 8.2 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)
• v5.3 (TiDB 5.3 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

Welcome @TopScrew!

It looks like this is your first PR to pingcap/docs-cn 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/docs-cn. 😃

[ti-chi-bot]

Hi @TopScrew. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[lilin90]

/ok-to-test

[TopScrew]

/ok-to-test

[TopScrew]

/ok-to-test

[bb7133]

LGTM

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #18633.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.3: #18634.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.3: #18635.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #18636.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #18637.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #18638.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.2: #18639.