Update API calls to the CMS Monitoring AlertManager

[nikodemas]

Impact of the new feature
WMCore central services (MSOutput maybe?)

Is your feature request related to a problem? Please describe.
Current API calls to AlertManager at /api/v1 will stop working in the new AlertManager version. See this error message shared by @amaltaro before:

2024-07-17 00:05:37,516:ERROR:MSCore: Failed to send alert to http://cms-monitoring.cern.ch:30093/api/v1/alerts. Error: (28, 'Failed to connect to cms-monitoring.cern.ch port 30093: Connection timed out
')

Describe the solution you'd like
Switch API calls to api/v2

[vkuznet]

Here is list of PRs related to WM configuration:

• for all dev cluster (test branch): https://gitlab.cern.ch/cmsweb-k8s/services_config/-/merge_requests/357
• for testbed cluster (preprod branch): https://gitlab.cern.ch/cmsweb-k8s/services_config/-/merge_requests/358
• for production cluster (prod branch): https://gitlab.cern.ch/cmsweb-k8s/services_config/-/merge_requests/359

Once they are reviewed and merged we still need to update all configuration files on dev/testbed/prod clusters to use them for running services.

[amaltaro]

@vkuznet don't we have to change anything else? Is v1 and v2 API completely compatible and with the same signature?
Can you please test this out by creating an actual alert with the v2 API?