Fix cert-exporter alerting

[QuentinBisson]

Before adding a new alerting rule into this repository you should consider creating an SLO rules instead.
SLO helps you both increase the quality of your monitoring and reduce the alert noise.

• How to create a SLO rule: https://github.com/giantswarm/sloth-rules#how-to-create-a-slo
• Documentation: https://intranet.giantswarm.io/docs/monitoring/slo-alerting/

---

Towards: https://github.com/giantswarm/...

This PR ensures that cert-exporter alerts page everywhere because it's deployed on all providers

Checklist

• Update CHANGELOG.md
• Add Unit tests
• Follow Alert structure
• Consider creating a dashboard (guidelines) (if it does not exist already) to help oncallers monitor the status of the issue.
• Request review from oncall area, as well as team (e.g: oncall-kaas-cloud GitHub group).

[hervenicol]

Why was it defining that certExporter is not installed in cloud-director, capvcd and capa? I guess it is, right? 🤔

Anyway, I guess this one will page if certExporter is not actually installed and you don't have any cert_exporter_not_after metrics.

Also: don't we have a parent issue for this?

[QuentinBisson]

I think it was because it was not installed in the past but it is now.

I'm reviewing alerts for multi-provider MCs but this one is a bit gray so no parent issues :(