Move patroni-registry CPU saturation to separate alert

The CPU saturation alert for patroni-registry is very noisy because the utilization is so low most of the time. We should set some kind of base limit that works so that regular spikes that are less than 30% don't trigger alerts.

Deliverable

• Remove patroni-registry from this alert
• Add second custom alert to handle the low overall saturation level.