Chore: Warlock testing and refactor

Problem Statement

The Warlock websocket component of Hazaar needs to be tested and refactored to ensure compatibility with recent framework changes. Currently, there are no unit tests, and the stability of the server must be verified before release. Additionally, issue #289 covers splitting the signal and messaging handler features from the code execution features, so this must be considered during the refactor.

Who will benefit?

This update will benefit developers using the Warlock websocket server within Hazaar by ensuring it remains stable, compatible, and maintainable with the latest framework changes.

Benefits and risks

Benefits:

• Ensures compatibility with the latest Hazaar framework updates.
• Improves maintainability and reliability of the Warlock websocket component.
• Introduces unit tests to validate functionality and prevent regressions.

Risks:

• Potential breaking changes if the refactor is not carefully managed.
• Additional development time required to implement unit tests.

Proposed solution

• Conduct a full compatibility review of the Warlock websocket component.
• Refactor the code as needed to align with framework changes.
• Implement unit tests to cover key functionality.
• Ensure that issue #289 is accounted for, with signal and messaging handlers separated from code execution.

Examples

No direct examples, but other websocket frameworks such as Ratchet or Swoole have structured implementations that could be referenced for best practices.

Priority/Severity

• High (This will bring a huge increase in performance/productivity/usability/legislative cover)