Introduction of drupal/hux

Problem/Motivation

As outlined in our decision record, we have identified the need to integrate Hux instead of relying on traditional hooks for managing interactions and events with.

Related decision records:

- https://open-social.slite.com/api/s/4jL3Wi0yd0mpI6/0019-Move-hooks-to-cl...
- https://open-social.slite.com/api/s/x8qsXcVBXG9vb0/0020-Adopt-HUX-as-a-O...

Proposed resolution

We will migrate from the current hook-based implementation to Hux. The Hux library offers a more modern and modular approach for handling events, making the system easier to maintain and extend in the long term.
Blog post on how to: https://www.previousnext.com.au/blog/hux-alternative-to-hooks
Drupal seems to go the same way: https://www.drupal.org/node/3442349 →

Remaining tasks

User interface changes

API changes

It's suggested to stop using standard hooks in the profit of service class hooks.
Example https://www.previousnext.com.au/blog/hux-alternative-to-hooks