Services in maintenance don't export the critical status to peered clusters

#### Overview of the Issue

Services put in maintenance with `consul maint` don't get their status set to critical on the peered cluster, it simply appears with empty healthchecks
---

As stated in the docs
https://developer.hashicorp.com/consul/commands/maint
> Under the hood, maintenance mode is activated by registering a health check in critical status against a service, and deactivated by deregistering the health check.

#### Reproduction Steps

- 2 dcs peered with each other
- service A registered in dc X
- service A put in maintenance in/ dc X
- on the other dc, healthchecks that were passing are now empty
- maintenance instance still showing up on `.service..peer.consul` and in prepared queries where `passing_only` is not `true`