Monitoring namespace service entries conflict
Grafana and Monitoring packages both create [outbound routes](https://repo1.dso.mil/big-bang/bigbang/-/blob/master/chart/templates/monitoring/values.yaml?ref_type=heads#L109-115) that are named the same thing, which creates contention over who owns the ServiceEntry.
This results in driftDetection trying to correct the ownership. You can see the events on the HelmReleases:
```bash
Normal DriftCorrected 3m3s (x4239 over 15h) helm-controller Cluster state of release monitoring/monitoring-monitoring.v1 has been corrected: ServiceEntry/monitoring/bb-tests-external configured
```
We should give these unique names.
issue