#10024: Add Render blueprint for OpenClaw

<!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR updates the Render blueprint (`render.yaml`) to include Gateway bind/port environment variables for the OpenClaw service. In practice, these values influence how the Gateway listens for control/UI traffic and how derived services compute their ports; they should match OpenClaw’s security expectations and deployment model (e.g., localhost-only vs LAN/Tailscale exposure). <h3>Confidence Score: 3/5</h3> - This PR is close, but the Render defaults as written are likely to trigger a critical security finding and expose the Gateway unexpectedly. - Only a small YAML change, but it sets `OPENCLAW_GATEWAY_BIND=lan` by default without configuring corresponding gateway auth, which is treated as a critical misconfiguration by the codebase’s own security audit and can widen access on hosted environments. - render.yaml <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->