Please update the deployment document.

### Check Ahead

- [x] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate.

- [ ] I am willing to try to fix this bug myself.

### Ⅰ. Issue Description

_No response_

### Ⅱ. Describe what happened

Please update the deployment document. After various attempts, I finally used docker compose to deploy and finally got 2.3.0 running. However, after upgrading to 2.4.0, it failed to start again.

According to the sample configuration in the source code, seata-naming-server was running, but starting seata-server failed, and the error log was: "A component required a bean of type 'org.springframework.boot.autoconfigure.web.ServerProperties' that could not be found."

### Ⅲ. Describe what you expected to happen

_No response_

### Ⅳ. How to reproduce it (as minimally and precisely as possible)

1. 2.3.0
2. 2.4.0

### Ⅴ. Anything else we need to know?

_No response_

### Ⅵ. Environment

docker compose

Start with the deployment document and the source-code sample configuration used for Docker Compose, comparing the 2.3.0 and 2.4.0 setups. Reproduce the upgrade and inspect the seata-server startup log for the missing ServerProperties bean. Done means the deployment document supports a working 2.4.0 Docker Compose deployment and accurately reflects the required configuration.

Written by the indexing model from the issue text.