docs: upadate Chinese installation docs

[guitu168]

Description

Updated Chinese installation documentation.
This PR is only responsible for the internationalization and synchronization of English changes from #6964.

Fixes # (issue)

Checklist

• I have explained the need for this PR and the problem it solves
• I have explained the changes or the new features added to this PR
• I have added tests corresponding to this change
• I have updated the documentation to reflect this change
• I have verified that this change is backward compatible (If not, please discuss on the APISIX mailing list first)

[moonming]

I think the previous directory structure is correct, according to different installation methods such as docker, RPM, and source code.

[moonming]

the file name is "how to build", which is means build from source code, not how to install.
And I think we can add doc for how to install.

[guitu168]

the file name is "how to build", which is means build from source code, not how to install. And I think we can add doc for how to install.

@moonming

1. The file name of how-to-build has not been changed because it is currently referenced in some documents, so it has not been changed for the time being. I will investigate and solve this problem later.
2. For the directory structure, it will be better to use the advanced features of Docusaurus to present the way, which allows the user to see the installation method he wants more intuitively.
3. For the way to build from source. We can probably move it to the GitHub repo as users installing from source would likely be checking on GitHub.
   If you have other suggestions, welcome to discuss.

[juzhiyuan]

the file name is "how to build", which is means build from source code, not how to install. And I think we can add doc for how to install.

@moonming

1. The file name of how-to-build has not been changed because it is currently referenced in some documents, so it has not been changed for the time being. I will investigate and solve this problem later.
2. For the directory structure, it will be better to use the advanced features of Docusaurus to present the way, which allows the user to see the installation method he wants more intuitively.
3. For the way to build from source. We can probably move it to the GitHub repo as users installing from source would likely be checking on GitHub.
   If you have other suggestions, welcome to discuss.

@moonming

1. The inconsistency between the filename and the sidebar label was a long time ago. This PR is only responsible for the internationalization and synchronization of English changes from docs: update "Installation" guide #6964;
2. The problem of inconsistency between the file name and the title should be corrected in the new PR. As for the historical link reference problem, @SkyeYoung could help to redirect the client to the document site to solve it. The file name can be modified to installation.md;
3. Building from source can be explained in a separate document (e.g., README, separate documentation for installation from source, adding a new Tab in current page to provide "How to build from source code").

cc @hf400159 @navendu-pottekkat @kwanhur @spacewander @SylviaBABY @yzeng25 @membphis

[moonming]

• For the directory structure, it will be better to use the advanced features of Docusaurus to present the way, which allows the user to see the installation method he wants more intuitively.

You didn't get my point. I mean, the user installs either via docker or via rpm, only one way. Therefore, the first-level directory must be the installation method.

[moonming]

• The inconsistency between the filename and the sidebar label was a long time ago. This PR is only responsible for the internationalization and synchronization of English changes from docs: update "Installation" guide #6964;

please create a issue for this, thx

[moonming]

1. This PR is only responsible for the internationalization and synchronization of English changes from docs: update "Installation" guide #6964;

Got it. @hf400159 please add this desc in this PR, Otherwise others do not know

[moonming]

the file name is "how to build", which is means build from source code, not how to install. And I think we can add doc for how to install.

@moonming

1. The file name of how-to-build has not been changed because it is currently referenced in some documents, so it has not been changed for the time being. I will investigate and solve this problem later.
2. For the directory structure, it will be better to use the advanced features of Docusaurus to present the way, which allows the user to see the installation method he wants more intuitively.
3. For the way to build from source. We can probably move it to the GitHub repo as users installing from source would likely be checking on GitHub.
   If you have other suggestions, welcome to discuss.

@moonming

1. The inconsistency between the filename and the sidebar label was a long time ago. This PR is only responsible for the internationalization and synchronization of English changes from docs: update "Installation" guide #6964;
2. The problem of inconsistency between the file name and the title should be corrected in the new PR. As for the historical link reference problem, @SkyeYoung could help to redirect the client to the document site to solve it. The file name can be modified to installation.md;
3. Building from source can be explained in a separate document (e.g., README, separate documentation for installation from source, adding a new Tab in current page to provide "How to build from source code").

cc @hf400159 @navendu-pottekkat @kwanhur @spacewander @SylviaBABY @yzeng25 @membphis

I mean we don't need to install etcd if install from docker.

[guitu168]

@juzhiyuan Since the documentation for building from source has not yet been created, there is no building from source tag added to this documentation. We will update this document later, not now.

@moonming I will modify the content of the document so that the first level directory is the installation method.

[moonming]

is there a preview link for docs？

[SkyeYoung]

@hf400159 Hi, we can use https://surge.sh/ to publish a preview quickly. 😊 (follow README Guide, build, then use surge publish)

[guitu168]

@moonming I have no way to upload to suger because of my network issues. You can take a look at this screenshot.

[moonming]

@hf400159 Hi, we can use https://surge.sh/ to publish a preview quickly. 😊 (follow README Guide, build, then use surge publish)

please create issue for this

[guitu168]

@hf400159 Hi, we can use https://surge.sh/ to publish a preview quickly. 😊 (follow README Guide, build, then use surge publish)

please create issue for this

cc @moonming issue link 1076