🐛Warning for no ingress rule when using remote managed tunnel with credentials-file

**Describe the bug**
When using the remote managed tunnel with a credentials file as an argument to cloudflared, there is still a warning "WRN No ingress rules were defined in provided config (if any) nor from the cli, cloudflared will return 503 for all incoming HTTP requests" in the logs, even though there are rules defined in the Zero Trust Dashboard, which are also successfully loaded afterwards and working.

**To Reproduce**
Steps to reproduce the behavior:
1. Create a tunnel within the Zero Trust Dashboard, including ingress rules
2. Start Cloudflared container with credentials-file argument:
`tunnel --credentials-file /tunneltoken.json --loglevel warn run Home`

**Expected behavior**
No warning should be shown since all relevant information are there and everything is working.

**Environment and versions**
- Debian 12
- Docker version 28.3.3
- Cloudflared docker image version 2025.8.0 (but issue has been there for at least a year)

**Logs and errors**
`2025-08-15T14:19:41Z WRN No ingress rules were defined in provided config (if any) nor from the cli, cloudflared will return 503 for all incoming HTTP requests`

**Additional context**
I think this is related to #933. In that issue, the fix was to suppress the warning if the --token flag was used. In my case, I'm using the --credentials-file flag, not the --token flag, so I still get the warning.