fix(config): guard WECOM_CALLBACK_PORT/BLUEBUBBLES_WEBHOOK_PORT against malformed env var

[vanthinh6886]

Summary

Replace bare int(os.getenv(...)) with env_int(...) for 2 port env vars in gateway/config.py:

• WECOM_CALLBACK_PORT (line 1834)
• BLUEBUBBLES_WEBHOOK_PORT (line 1890)

A malformed value (e.g. WECOM_CALLBACK_PORT=abc) causes a ValueError crash during gateway config loading. The env_int() helper in utils.py catches ValueError/TypeError and returns the default value.

Changes

• gateway/config.py: Add env_int to existing utils import, replace 2 bare int(os.getenv) calls

Test Plan

• pytest config/wecom/bluebubbles tests pass
• Lint clean

Context

Part of systemic env var guard issue. Related: PR #48735 (api_server.py), PR #48740 (run.py), PR #48745 (email.py).

[alt-glitch]

Duplicate of #20205 — same two port env vars (WECOM_CALLBACK_PORT, BLUEBUBBLES_WEBHOOK_PORT) guarded against malformed values with the same int-guard helper in gateway/config.py. #20205 (earliest open) already covers this exact site/mechanism.

[tonydwb]

Code Review Summary

Verdict: Approved

Guards WECOM_CALLBACK_PORT and BLUEBUBBLES_WEBHOOK_PORT against malformed env var values. Consistent with the env-var guard pattern in this batch. 3 additions. No concerns.

---

Reviewed by Hermes Agent

[kshitijk4poor]

Closing as superseded by #49558, which landed the canonical fix for this whole bug class.

#49558 adds env_float() alongside the existing env_int() in utils.py (the env_float helper was cherry-picked from this PR — @annguyenNous's authorship is preserved in the merge, commit 06ca1e998), then converts all 22 genuinely-unguarded first-party int/float(os.getenv()) sites across the gateway, agent, auth, and platform adapters to those canonical helpers.

We went with the utils.env_int/env_float route (the established house pattern, already imported in several modules) rather than per-module helpers or inline try/except, so every malformed-env crash site is now guarded through one shared implementation.

Thanks for spotting and driving the fix on this — it's all in main now via:
#49558