docs: add ADC and Ingress Controller tabs to limit-req plugin docs

[Yilialinn]

Description

Port limit-req plugin documentation with all three configuration tabs (Admin API, ADC, Ingress Controller) for all example sections.

Changes

• Add ADC and Ingress Controller (Gateway API + APISIX CRD) tabs to all example sections
• Add "Local vs Redis Rate Limiting" section explaining the two modes
• Fix rate and burst attribute types from integer to number to match source code
• Fix key attribute to be required with no default (was incorrectly showing remote_addr as default)
• Fix redis_cluster_nodes description from "at least two addresses" to "at least one address"
• Fix ZH doc: correct bust typo to burst, remove duplicate allow_degradation row, remove non-existent show_limit_quota_header attribute, fix redis_cluster_name table formatting

[Copilot]

Pull request overview

This PR updates the limit-req plugin documentation to provide consistent, multi-environment configuration examples (Admin API / ADC / Ingress Controller) and to align documented attributes with the actual plugin schema.

Changes:

• Add ADC and Ingress Controller (Gateway API + APISIX CRD) tabs to all example sections.
• Add a “Local vs Redis Rate Limiting” section describing the two enforcement modes.
• Correct attribute documentation to match source code (e.g., rate/burst types, required key, Redis cluster node requirements).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/zh/latest/plugins/limit-req.md	Adds multi-tab examples, adds local-vs-Redis explanation, and corrects the ZH attribute table and typos.
docs/en/latest/plugins/limit-req.md	Adds multi-tab examples, adds local-vs-Redis explanation, and updates the EN attribute table to match schema.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

In the “Apply Rate Limiting by Remote Address” example, this note says the key applies quota by remote address and consumer, but the configuration only uses remote_addr and does not involve consumer identity. Please adjust the wording to avoid implying consumer-based limiting here.

Suggested change

	❷ `key`: set to `remote_addr` to apply rate limiting quota by remote address and consumer.
	❷ `key`: set to `remote_addr` to apply rate limiting quota by remote address.

[Copilot]

The key_type description has a grammatical error (“interpreted a variable” / “interpreted as a combination…” is missing “as”). Please update these phrases (e.g., “interpreted as a variable”) to improve clarity.

Suggested change

	| key_type | string | False | var | ["var", "var_combination"] | The type of key. If the `key_type` is `var`, the `key` is interpreted a variable. If the `key_type` is `var_combination`, the `key` is interpreted as a combination of variables. |
	| key | string | True | | | The key to count requests by. If the `key_type` is `var`, the `key` is interpreted a variable. The variable does not need to be prefixed by a dollar sign (`$`). If the `key_type` is `var_combination`, the `key` is interpreted as a combination of variables. All variables should be prefixed by dollar signs (`$`). For example, to configure the `key` to use a combination of two request headers `custom-a` and `custom-b`, the `key` should be configured as `$http_custom_a $http_custom_b`. |
	| key_type | string | False | var | ["var", "var_combination"] | The type of key. If the `key_type` is `var`, the `key` is interpreted as a variable. If the `key_type` is `var_combination`, the `key` is interpreted as a combination of variables. |
	| key | string | True | | | The key to count requests by. If the `key_type` is `var`, the `key` is interpreted as a variable. The variable does not need to be prefixed by a dollar sign (`$`). If the `key_type` is `var_combination`, the `key` is interpreted as a combination of variables. All variables should be prefixed by dollar signs (`$`). For example, to configure the `key` to use a combination of two request headers `custom-a` and `custom-b`, the `key` should be configured as `$http_custom_a $http_custom_b`. |

[Copilot]

此处说明 key 会“按远程地址和消费者”应用配额，但本示例仅使用 remote_addr，未涉及消费者信息（也未启用认证插件）。建议把表述改为仅按远程地址进行速率限制，避免误导。

Suggested change

	❷ `key`：设置为 `remote_addr`，以按远程地址和消费者应用速率限制配额。
	❷ `key`：设置为 `remote_addr`，以按远程地址应用速率限制配额。

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.