[Doc] docs/en/Configuration_Client.md lists client parameters that do not exist in the Java client #11279

Description

docs/en/Configuration_Client.md documents several client configuration parameters that do not exist in this repository's Java (remoting) client, so following the doc produces code that does not compile.

Rows in the page (added by #9258's "5.x compatibility" update) that have no corresponding field/setter on current develop:

• Common configuration table: autoUpdateNameServer, instanceId — ClientConfig has neither (the real instance identifier is instanceName, which the table already documents in a separate row).
• Producer table: enableBatchSend, enableBackPressure — neither exists on DefaultMQProducer.
• Push consumer table: the Rebalance Strategies (5.x) row places a strategy class name in the "Parameter Name" column; it is not a settable parameter at all.
• Pull consumer table: messageGroup — DefaultMQPullConsumer has no such property.
• Message data-structure table: messageGroup (5.x) — Message has no such field.

Verification: grep -r "autoUpdateNameServer\|enableBackPressure\|enableBatchSend\|messageGroup" client/src/main/java common/src/main/java finds no such client properties on current develop. (messageGroup-style group FIFO ordering is a concept of the separate gRPC clients, not this Java client.)

Additional quoting problem in the same page

The multi-NameServer environment-variable example is:

export NAMESRV_ADDR=192.168.0.1:9876;192.168.0.2:9876

In a shell the unquoted ; terminates the export command, so NAMESRV_ADDR only receives the first address and 192.168.0.2:9876 is executed as a (failing) command. It should be quoted:

export NAMESRV_ADDR='192.168.0.1:9876;192.168.0.2:9876'

Expected behavior

Every parameter documented in Configuration_Client.md should exist on the Java client classes the page covers, and the shell examples should be copy-paste safe.