The JVM startup parameters for release packages and Docker files are not uniform

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

### Ⅰ. Issue Description
JVM startup parameters are not uniform and difficult to maintain. It is hoped that the JVM parameters can be maintained in only one place.

release package：
https://github.com/seata/seata/blob/develop/distribution/bin/seata-server.sh

docker image startup parameters by jib
https://github.com/seata/seata/blob/0cdaa08ec8f1ad060bb01a770cbc5d02c3ed6350/server/pom.xml#L279

### Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

```
Just paste your stack trace here!
```

### Ⅲ. Describe what you expected to happen

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

1. xxx
2. xxx
3. xxx

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

### Ⅵ. Environment:

- JDK version :
- Seata version:
- OS :
- Others:

Compare the JVM startup parameters in distribution/bin/seata-server.sh with the Jib configuration around server/pom.xml#L279. Trace how each release package and Docker image receives its parameters, then verify that both startup paths use one maintained set of JVM parameters.

Written by the indexing model from the issue text.