Multiple filter chains with overlapping matching rules are defined

### Nomad version
```
nomad version
Nomad v2.0.0
BuildDate 2026-04-21T15:42:13Z
Revision 7a90601f4d9bc473718311fe5167c0c1f66500ba
root@nomad-client15:~# consul version
Consul v1.19.2
Revision 048f1936
Build Date 2024-08-27T16:06:44Z
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
```
### Operating system and Environment details
Ubuntu 22.04.5 LTS
### Issue
After upgrading Nomad dev cluster from 1.8.3 to 2.0 and Consul v1.19.2 to v1.22.7 get this error:
```
May 15 00:36:45 nomad-client15 consul[284309]: error=
May 15 00:36:45 nomad-client15 consul[284309]: | rpc error: code = Internal desc = Error adding/updating listener(s) outbound_listener:127.0.0.1:15001: error adding listener '127.0.0.1:15001': multiple filter chains with overlapping matching rules are defined
```
### Reproduction steps
I'm not sure what exactly is causing this as I can't reproduce it on a single node test cluster.
I understand that I have provided little information, but perhaps you can point me in the right direction. Or tell me what additional information you need.
Sometime `consul reload` helps to fix and when deploy new job or `systemctl restart consul` the error is returned
Later I will update the prod cluster so I can update Nomad step by step from 1.8 to 2.0 to see when it happen.
### Nomad job for example
[flows-consumer.txt](https://github.com/user-attachments/files/27783027/flows-consumer.txt)
### Client config
[nomad-client.txt](https://github.com/user-attachments/files/27783309/nomad-client.txt)

Start by reviewing the attached flows-consumer.txt Nomad job and nomad-client.txt configuration, then compare the reported Nomad and Consul versions and the upgrade sequence from Nomad 1.8.3 to 2.0 and Consul 1.19.2 to 1.22.7. Reproduce the failure around consul reload, job deployment, and Consul restart; done means identifying the configuration or sequence that creates overlapping filter chains and documenting a verified resolution.

Written by the indexing model from the issue text.