feat/add discord webhook support

[kln581]

This pull request introduces support for sending notification responses to Discord webhooks in ChatNotify, allowing users to forward triggered chat events to Discord servers. It adds new configuration options, updates the GUI to manage webhook settings, and implements the backend logic for sending webhook messages. The documentation and changelog are also updated to reflect these new features.

Discord Webhook Integration

• Added a new DISCORD response type to the Response.Type enum, enabling notifications to send messages to Discord webhooks.
• Implemented the DiscordWebhookHandler utility class to handle asynchronous sending of messages to Discord webhooks, including payload formatting and error handling.
• Updated ResponseUtil.tickResponses to handle the DISCORD response type and send messages via the webhook handler when enabled.

Configuration and GUI Enhancements

• Added discordWebhookEnabled and discordWebhookUrl fields to the Config class, with serialization/deserialization, default values, and version bump. [1] [2] [3] [4] [5] [6] [7]
• Updated the detection settings GUI (DetectionList) to allow users to enable/disable Discord webhook responses and enter the webhook URL. [1] [2]

Documentation and Changelog Updates

• Expanded the README to describe Discord webhook response functionality, including setup instructions and usage notes. [1] [2]
• Added an entry to the changelog for version 2.6.7 noting the addition of Discord webhook support.

Internal Improvements

• Updated the Response class to store the original triggering message for use in Discord webhook payloads.
• Refactored response sending logic to pass the triggering message to response handlers. [1] [2]

These changes enable powerful new integrations for ChatNotify users who want to monitor Minecraft chat events remotely via Discord.

[NotRyken]

I appreciate the effort for what it appears to be, but this is a non-starter for various reasons of which I've compiled a partial list below.

• noncompliant with .editorconfig
• not proofread
• nonsensical design decisions (notably but not exclusively settings location)
• clearly not tested