AlertOps alert transport

[ashwath129]

This is a request to add this Transport publicly, so alerts can be sent to AlertOps' webhook endpoint - AlertOps is an alerting/notification tool. (https://alertops.com/)

Please give a short description what your pull request is for

DO NOT DELETE THE UNDERLYING TEXT

Please note

Please read this information carefully. You can run ./lnms dev:check to check your code before submitting.

• Have you followed our code guidelines?
• If my Pull Request does some changes/fixes/enhancements in the WebUI, I have inserted a screenshot of it.
• If my Pull Request makes discovery/polling/yaml changes, I have added/updated test data.

Testers

If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926
After you are done testing, you can remove the changes with ./scripts/github-remove. If there are schema changes, you can ask on discord how to revert.

[CLAassistant]

All committers have signed the CLA.

[electrocret]

Please add documentation to doc/Alerting/Transports.md on how to configure this Alert Transport.

[ashwath129]

Please add documentation to doc/Alerting/Transports.md on how to configure this Alert Transport.

Sure did this ! - #16058

[murrant]

@ashwath129 can you please put the docs in this PR (that way it is easy to find them later).
If you don't know how to do that, come ask on Discord.

[electrocret]

@murrant , sorry didn't see your comment before approving these.

Yeah, it's best practice to have all the changes under a single PR, however in this instance it shouldn't be too much of an inconvenience since it's just a single transport that doesn't seem to have anything out of the ordinary going on.

[librenms-bot]

This pull request has been mentioned on LibreNMS Community. There might be relevant details there:

https://community.librenms.org/t/24-6-0-changelog/24707/1