fix(config): migrate device API URLs to kikivok domain

docs/device-fortune-controller-api.md

@@ -14,7 +14,7 @@
 The complete path through the gateway is normally:
 
 ```text
-POST https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth
+POST https://gz.api.kikivok.com/token/api/device/fortune/daily-wealth
 ```
 
 When connecting directly to the token service, use its deployed port, for example:
@@ -91,7 +91,7 @@ The response field names are part of the current server contract and are intenti
 ### Windows PowerShell
 
 ```powershell
-curl.exe -X POST "https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth" `
+curl.exe -X POST "https://gz.api.kikivok.com/token/api/device/fortune/daily-wealth" `
   -H "Content-Type: application/json" `
   -d "{\"deviceId\":\"test-device\",\"birthYear\":1998,\"birthMonth\":5,\"birthDay\":21,\"birthHour\":14,\"birthMinute\":30,\"birthPlace\":\"广东省广州市\",\"currentResidence\":\"广东省深圳市\",\"mbti\":\"INFJ\",\"timezone\":\"Asia/Shanghai\",\"targetDate\":\"2026-06-08\"}"
 ```
@@ -99,7 +99,7 @@ curl.exe -X POST "https://gz.api.talkingq.com/token/api/device/fortune/daily-wea
 ### Linux and macOS
 
 ```bash
-curl -X POST "https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth" \
+curl -X POST "https://gz.api.kikivok.com/token/api/device/fortune/daily-wealth" \
   -H "Content-Type: application/json" \
   -d '{
     "deviceId": "test-device",
@@ -118,11 +118,11 @@ curl -X POST "https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth"
 
 ### HTTP
 
-Send this HTTP/1.1 request over TLS to `gz.api.talkingq.com`:
+Send this HTTP/1.1 request over TLS to `gz.api.kikivok.com`:
 
 ```http
 POST /token/api/device/fortune/daily-wealth HTTP/1.1
-Host: gz.api.talkingq.com
+Host: gz.api.kikivok.com
 Content-Type: application/json
 
 {