Consul service discovery is occurring even though the service health check is failing.

**Consul service discovery is occurring even though the service health check is failing.**

#### Overview of the Issue

Consul servers are running with version 1.18.2.

Client-1 node is running with version 1.20.2.
Client-2 node is running with version 1.20.2 (where app2 service is running).
Client-3 node is running with version 1.18.2 (where app3 service is running).
Service discovery for app2 and app3 is occurring from Client-1 and Client-2 nodes, even though the health status of app2 and app3 services is critical. However, service discovery is not occurring from Client-3 node.

It seems this issue occurs when the Consul client version is 1.20.2 and the Consul server is on a lower version.

---

#### Reproduction Steps

Set Consul servers to version 1.18.2 and the Consul client node to version 1.20.2.
Then, set the health of the service running on the client node to critical and perform a lookup of that service from the client node.

-->

### Consul info for both Client and Server

consul servers: 1.18.2
consul client: 1.20.2

Client info

```
Output from client 'consul info' command here
```

```
Client agent HCL config
```

Server info

```
Output from server 'consul info' command here
```

```
Server agent HCL config
```

### Operating system and Environment details

### Log Fragments

Start by reproducing the lookup with Consul servers at 1.18.2 and clients at 1.20.2, using the reported critical health status and comparing behavior across clients. The report names no source files or tests; done means service discovery consistently excludes the critical app2 and app3 services, with a regression test covering the version combination.

Written by the indexing model from the issue text.