🐞 [BUG] - Config editor shows "invalid port range" error when using env variable in inbound port

[ingria]

Integrity requirements

• I provided the complete config and logs, rather than just providing the truncated parts based on my own judgment.
• I searched issues and did not find any similar issues.
• The problem can be successfully reproduced in the latest release

Description

Everything works fine (backend seems to understand this syntax), but there's an error above the editor.

Reproduction Method

Add "port": "env:SOME_ENV_VARIABLE" to inbound config