Bind UI-created alert contacts to reviewed integration IDs

Bind UI-created alert contacts to their reviewed integration IDs instead of assuming they will have the IDs chosen by an API provisioning script. Make any override explicit and validate that the full expected set is unique and well formed. Continue checking each contact's type, destination and recovery behavior exactly.

Include those IDs in the acceptance digest so replacing a contact invalidates older delivery evidence. This handles mixed UI/API setup without weakening the activation gate or granting a new setup credential merely to control resource naming. It does not prove live routing or allow unknown receivers to pass verification.

Applies when: Alert contacts are created through a UI but independently verified by provisioning or activation tooling. Keywords: Grafana alert contact integration UID UI provisioning activation digest verification