fix(execute-service): update startupProbe to /health/ready with 30 failureThreshold

The service was 'running but not ready' because:
- startupProbe used /health (always-ok) with only failureThreshold: 6 (~30s grace)
- Executor initialization (Hyperliquid SDK network calls + Solana client) takes longer

Now uses /health/ready (checks actual executor state) with failureThreshold: 30 (~5min grace), matching the pattern used for data-service and dashboard.

Also updated Helm template for consistency.

apps/base/customer1/trading-platform/execute-service/deployment.yaml

@@ -65,11 +65,11 @@ spec:
                   key: JWT_SECRET_KEY
           startupProbe:
             httpGet:
-              path: /health
+              path: /health/ready
               port: 8002
             initialDelaySeconds: 15
-            periodSeconds: 5
-            failureThreshold: 6
+            periodSeconds: 10
+            failureThreshold: 30
           livenessProbe:
             httpGet:
               path: /health