feat(io): joystick support

- Updated the docker image and the sight-gitlab references
- Implemented `sight::io::joystick::interactor`, `sight::io::joystick::detail::event_loop` and a module `sight::modules::io::joystick`.

#### sight::modules::io::joystick module

Controls the global joystick `event_loop` instance.

Basically, it starts it when `sight::modules::io::joystick::plugin::start()` is called and stops it on `sight::modules::io::joystick::plugin::stop()`. Once started, registered `interactor` will start receiving joystick events.

There is a unit test (`sight::module::io::joystick::ut`) which demonstrates basic usage, the support of module unloading, etc..

#### sight::io::joystick::detail::event_loop class

This is where the whole implementation is. It is a singleton that uses a timer to poll for SDL events on the main thread. When one is catch, it is simply forwarded to the registered `interactor` with specific callback functions. It implies that all callback functions are executed on the main thread, so you may have to protect the access if your service runs on a specific worker.

The code of `instance()` could have been simpler, but, since we are dealing with posted tasks on the main thread, special care has been needed to let the instance die without making waiting tasks crash.

#### sight::io::joystick::interactor interface

This register / unregister automatically to the `event_loop` any class that inherits from it. Then, these callbacks will be available:

``` c++ 
    void joystick_axis_motion_event(const axis_motion_event& _event);
    void joystick_axis_direction_event(const axis_direction_event& _event);
    void joystick_hat_motion_event(const hat_motion_event& _event);
    void joystick_ball_motion_event(const ball_motion_event& _event);
    void joystick_button_pressed_event(const button_event& _event);
    void joystick_button_released_event(const button_event& _event);
    void joystick_added_event(const joystick_event& _event);
    void joystick_removed_event(const joystick_event& _event);
```

All callbacks use "event" structures, which should provides all needed information (device name, index, guid, axis, buttons, ...). Indeed, almost all of what is available from SDL is forwarded.
Additionally, it is possible to list all attached devices with `devices()` and to temporary stop receiving event with `block_events(bool)`.

> `joystick_axis_direction_event` is derived from `joystick_axis_motion_event`, but instead of sending the axis values on every change, it converts it to "up" or "down", and is only trigered once, until the axis goes back to neutral.

Author: dweckmann

.gitlab-ci.yml

@@ -7,10 +7,10 @@ stages:
 
 include:
     - project: "sight/sight-gitlab"
-      ref: cedfea7a6437cb7c31e6cac1ca58e6428e9cb2cc
+      ref: a3ad77bb7cf077b97e1d56b7f3326ea57b061ca7
       file: "/.templates/deploy.yml"
     - project: "sight/sight-gitlab"
-      ref: cedfea7a6437cb7c31e6cac1ca58e6428e9cb2cc
+      ref: a3ad77bb7cf077b97e1d56b7f3326ea57b061ca7
       file: "/.templates/build.yml"
 
 lint:ubuntu-24.04:

libs/io/CMakeLists.txt

@@ -7,3 +7,4 @@ add_subdirectory(opencv)
 add_subdirectory(dimse)
 add_subdirectory(session)
 add_subdirectory(bitmap)
+add_subdirectory(joystick)

libs/io/joystick/CMakeLists.txt

@@ -0,0 +1,15 @@
+sight_add_target(
+    io_joystick
+    TYPE LIBRARY
+    WARNINGS_AS_ERRORS ON
+    OBJECT_LIBRARY ON
+)
+
+# find_package(SDL2 CONFIG REQUIRED) done in Dependencies.cmake
+target_link_libraries(${TARGET_OBJECT_LIB} PRIVATE SDL2::SDL2)
+
+target_link_libraries(${TARGET_OBJECT_LIB} PRIVATE core)
+
+if(SIGHT_BUILD_TESTS)
+    add_subdirectory(test)
+endif()

libs/io/joystick/Dependencies.cmake

@@ -0,0 +1 @@
+find_package(SDL2 CONFIG REQUIRED)