feat(backend): adding idle and polling mechanism to imap

[Shadow243]

Summary

This PR introduces a backend service that includes:

• Event dispatching system for triggering and handling system-wide events.
• Task scheduling using cron-like jobs with overlapping prevention.
• Real-time notifications via multiple channels (e.g., Telegram, SMS, Slack).
• Ratchet PHP lib integration

Key Features

• Event Class: Implements an event dispatching system where events can be defined and dispatched across the system. This allows for decoupled execution of processes in response to events.

• Scheduler: Manages task scheduling with cron-like expressions, mutex handling to prevent task overlapping, and timezone support.

• Commands: Defines and executes registered commands with dependency injection support.

• Notifications: Notification system with extensible drivers for various channels (e.g., Telegram, SMS, Slack). It allows sending notifications based on event triggers such as new emails.

• Listeners: Allows the system to react to dispatched events by triggering actions such as notifications or logging.

Example Usage Command using database queue driver

Example Usage Command using sqs queue driver

• Related Issue: webhook notification #178
• Related PR: [ENH] Add telegram notification webhook when new messages are detected #1056
• Related RFC: https://datatracker.ietf.org/doc/html/rfc2177
• Related RFC: https://datatracker.ietf.org/doc/html/rfc822

[kroky]

Load the dependencies here and don't include index.php. Treat console as a separate entry point in the application. index.php will be for web requests and this one for cli.

[kroky]

Why do we define another package? It doesn't seem to be runnable without main cypht repo, so better stay as just a subdirecrory in this repo. No need for composer dependencies here.

[kroky]

Please ping me when you add the ratchet lib and polling, so I can review again.

[Shadow243]

Channels tested and fixed

[Shadow243]

schedule:work is also working correctly, i'm receiving Notification every minute as a planned:

[marclaporte]

We will soon release Cypht 2.5.0 so this MR is too big/risky to be part of it.

But after, we must decide if this is suitable for Cypht 2.6.x or rather 3.0.x

[Shadow243]

We will soon release Cypht 2.5.0 so this MR is too big/risky to be part of it.

But after, we must decide if this is suitable for Cypht 2.6.x or rather 3.0.x

I share that opinion.