docs(config_yaml): clarify DUBBO_GO_CONFIG_PATH resolution (#1097)

DUBBO_GO_CONFIG_PATH is resolved against the running process's working
directory, but the README only showed a relative form
(`../conf/dubbogo.yml`) that requires cd'ing into the `cmd` directory.
Users who run the more idiomatic `go run ./config_yaml/go-server/cmd/...`
from the repo root see dubbo.Load() panic with no clear hint about why.

Update both README.md and README_zh.md to:

- Recommend running from the repo root with an absolute path built via
  `$(pwd)/...`, which works regardless of where the user is.
- Keep the original cd + relative path form as an alternative.
- Add an explicit note explaining how the variable is resolved so users
  can debug their own setup.

Closes #1083

Author: Harry33t

config_yaml/README.md

@@ -31,15 +31,38 @@ cd path_to_dubbogo-sample/config_yaml/proto
 protoc --go_out=. --go-triple_out=. ./greet.proto
 ```
 ### Server
+
+Run from the repository root:
+
 ```bash
+export DUBBO_GO_CONFIG_PATH="$(pwd)/config_yaml/go-server/conf/dubbogo.yml"
+go run ./config_yaml/go-server/cmd/main.go
+```
+
+Or, if you prefer to `cd` into the `cmd` directory first, the relative path also works:
+
+```bash
+cd config_yaml/go-server/cmd
 export DUBBO_GO_CONFIG_PATH="../conf/dubbogo.yml"
-cd path_to_dubbogo-sample/config_yaml/go-server/cmd
 go run .
 ```
+
+> **Note**: `DUBBO_GO_CONFIG_PATH` is resolved against the working directory of the running process, so a relative value like `../conf/dubbogo.yml` only works when you launch the program from the `cmd` directory. Use an absolute path (as in the first example) to avoid this constraint.
+
 ### Client
+
+Run from the repository root (after the server is up):
+
+```bash
+export DUBBO_GO_CONFIG_PATH="$(pwd)/config_yaml/go-client/conf/dubbogo.yml"
+go run ./config_yaml/go-client/cmd/main.go
+```
+
+Or, with `cd`:
+
 ```bash
+cd config_yaml/go-client/cmd
 export DUBBO_GO_CONFIG_PATH="../conf/dubbogo.yml"
-cd path_to_dubbogo-sample/config_yaml/go-client/cmd
 go run .
 ```
 

config_yaml/README_zh.md

@@ -32,15 +32,38 @@ cd path_to_dubbogo-sample/config_yaml/proto
 protoc --go_out=. --go-triple_out=. ./greet.proto
 ```
 ### Server
+
+在仓库根目录下运行：
+
 ```bash
+export DUBBO_GO_CONFIG_PATH="$(pwd)/config_yaml/go-server/conf/dubbogo.yml"
+go run ./config_yaml/go-server/cmd/main.go
+```
+
+或者，先 `cd` 到 `cmd` 目录再运行（用相对路径也可以）：
+
+```bash
+cd config_yaml/go-server/cmd
 export DUBBO_GO_CONFIG_PATH="../conf/dubbogo.yml"
-cd path_to_dubbogo-sample/config_yaml/go-server/cmd
 go run .
 ```
+
+> **注意**：`DUBBO_GO_CONFIG_PATH` 是相对于程序运行时的工作目录解析的，所以 `../conf/dubbogo.yml` 这种相对路径只有在 `cmd` 目录下启动程序时才有效。如果想从其他目录启动，建议使用上面那种绝对路径。
+
 ### Client
+
+在仓库根目录下运行（服务端启动后）：
+
+```bash
+export DUBBO_GO_CONFIG_PATH="$(pwd)/config_yaml/go-client/conf/dubbogo.yml"
+go run ./config_yaml/go-client/cmd/main.go
+```
+
+或者先 `cd`：
+
 ```bash
+cd config_yaml/go-client/cmd
 export DUBBO_GO_CONFIG_PATH="../conf/dubbogo.yml"
-cd path_to_dubbogo-sample/config_yaml/go-client/cmd
 go run .
 ```