it is still output "Intent queue depth (4525) exceeds limit (4096), dropping messages!" in consul agent 1.13.6

#### Overview of the Issue

---

#### Reproduction Steps

### Consul info for both Client and Server
agent:
check_monitors = 0
check_ttls = 0
checks = 0
services = 0
build:
prerelease =
revision = 61547a41
version = 1.13.6
version_metadata =
consul:
acl = disabled
bootstrap = false
known_datacenters = 1
leader = false
leader_addr = 10.240.99.5:8300
server = true
raft:
applied_index = 724266105
commit_index = 724266105
fsm_pending = 0
last_contact = 40.149045ms
last_log_index = 724266105
last_log_term = 585
last_snapshot_index = 724265484
last_snapshot_term = 585
latest_configuration = [{Suffrage:Voter ID:3d6d1924-b803-ac4c-1080-e81c78ae29ad Address:10.240.99.5:8300} {Suffrage:Voter ID:ac665d3d-fae0-f6a0-67e1-63609cabee35 Address:10.240.99.7:8300} {Suffrage:Voter ID:d0554c6d-119a-d139-2c4c-8a6f4e3a9c84 Address:10.240.98.29:8300} {Suffrage:Voter ID:620eecc5-9dde-2e9c-543e-3f7ea6172ebf Address:10.240.99.6:8300}]
latest_configuration_index = 0
num_peers = 3
protocol_version = 3
protocol_version_max = 3
protocol_version_min = 0
snapshot_version_max = 1
snapshot_version_min = 0
state = Follower
term = 585
runtime:
arch = amd64
cpu_count = 8
goroutines = 2145
max_procs = 8
os = linux
version = go1.18.9
serf_lan:
coordinate_resets = 0
encrypted = false
event_queue = 0
event_time = 116
failed = 0
health_score = 0
intent_queue = 4153
left = 0
member_time = 1182621
members = 1073
query_queue = 0
query_time = 590
serf_wan:
coordinate_resets = 0
encrypted = false
event_queue = 0
event_time = 1
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 41373
members = 4
query_queue = 0
query_time = 1

Client info
1 at 2022，the amount of members is up 6000, slowly, the number is began reduce, at now ,the amount of members only near 1000
[root@pub-consul-05 tools]# ./consul members --http-addr 10.240.99.6:8500|wc -l
1074

2 at in the process of reducing, we use consul leave to get off the cluster

3 it can see many leave message ,but the leave action happden 2022,the node is not in cluster now


```
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

The payload names no source files or tests. Start by reproducing the Consul 1.13.6 behavior with `consul info`, focusing on the Serf LAN `intent_queue` and the reported warning, then compare it with the stale member and leave-message details. Done means the queue behavior and warning cause are reproducibly understood and the issue's expected handling is verified.

Written by the indexing model from the issue text.