Readiness check for some services returns `500` status code

related #8783 #10316

### Description
Checking the readiness of some services returns `500` status code:
- graph
- idp
- proxy

```console
curl -kv http://localhost:9124/readyz
```
Response:
```console
< HTTP/1.1 500 Internal Server Error
< Cache-Control: no-cache, no-store, max-age=0, must-revalidate, value
< Content-Type: text/plain
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Last-Modified: Tue, 26 Nov 2024 11:07:30 GMT
< Vary: Origin
< X-Graph-Version: 7.0.0-rc.2+9a7c8a43f8
< Date: Tue, 26 Nov 2024 11:07:30 GMT
< Content-Length: 21
<
* Connection #0 to host localhost left intact
Internal Server Error%
```

Likewise check for the service `auth-bearer` do not work.
```console
curl -kv http://localhost:9149/readyz
```

Response:
```console
* Trying 127.0.0.1:9149...
* connect to 127.0.0.1 port 9149 failed: Connection refused
* Trying ::1:9149...
* connect to ::1 port 9149 failed: Connection refused
* Failed to connect to localhost port 9149 after 0 ms: Connection refused
* Closing connection 0
curl: (7) Failed to connect to localhost port 9149 after 0 ms: Connection refused

```

## Logs
```
{"level":"error","service":"idp","error":"'ldap reachability': dial tcp: address ldaps://localhost:9235: too many colons in address","time":"2025-02-17T13:12:32+05:45","message":"check failed"}
{"level":"error","service":"graph","error":"'ldap reachability': dial tcp: address ldaps://localhost:9235: too many colons in address","time":"2025-02-17T13:12:48+05:45","message":"check failed"}
{"level":"error","service":"proxy","error":"'nats reachability': could not connect to nats server: dial tcp: lookup ocis-cluster on 127.0.0.53:53: server misbehaving","time":"2025-02-17T13:12:09+05:45","message":"check failed"}

```