Add Flowtriq notification plugin

[jacob-masse]

Summary

• Add a new notification plugin for Flowtriq, a DDoS detection and traffic analytics platform
• The plugin POSTs alert payloads (JSON) to a configurable webhook URL with optional API key authentication via X-API-Key header
• Follows the same patterns as existing webhook-based plugins (Slack, VictorOps, PagerDuty)

What's included

Plugin logic (cmk/notification_plugins/flowtriq.py):

• Builds a JSON payload with source, host, host_address, service, state, output, notification_type, and optional Checkmk url
• Sends via post_request with optional X-API-Key header
• Accepts 200, 201, and 202 as success status codes

Entry point script (notifications/flowtriq.py):

• Standard notification script entry point following existing patterns

WATO GUI form (cmk/gui/wato/_notification_parameter/_flowtriq.py):

• Webhook URL (explicit or from password store)
• Optional API key (stored securely via Checkmk password handling)
• SSL verification toggle, proxy, and URL prefix settings

Type definitions (cmk/utils/notify_types.py):

• FlowtriqPluginModel, FlowtriqPluginName, FlowtriqNotify
• Added to KnownPluginParameters, BuiltInPluginNames, NotifyPluginParamsDict unions

Tests:

• Unit tests covering service notification, host notification, and recovery scenarios
• Updated test_registry, test_configuration_entity, and test_binaries expected plugin lists

Build:

• Added to Bazel BUILD notification_scripts pkg_files renames

Test plan

• Unit tests pass for test_flowtriq.py (message construction for service, host, and recovery notifications)
• Notification parameter registry test includes flowtriq
• Configuration entity readable name resolves to "Flowtriq parameter"
• Integration binary smoke test exits with expected KeyError.*NOTIF when run without env vars
• End-to-end: configure Flowtriq notification in WATO, trigger a test notification, verify JSON payload arrives at webhook endpoint

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA.

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[jacob-masse]

I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA.

[jacob-masse]

recheck

[github-actions]

Thank you for your contribution. This pull request has been marked as stale as it has not passed the automated tests and there was no activity for the last 14 days.
Please take a look at the ‘Checks’ section for details on the test results and make the necessary changes.

This pull request will be closed due to inactivity after 60 days, if no action is taken.