In ConfigurGUI restrict SimpleSignals to only emit PySide6 Signals

[rocco8773]

ConfigureGUI as getting random segmentation faults when a motor was moving. This was linked back to to Motor SimpleSignals being connected to AxisControlWidget.update_display_of_axis_status. This is inherently an unsafe thread operation since the AxisControlWidget is running in a thread managed by Qt, whereas the SimpleSingal could have been executed in the thread running the Motor's asyncio loop.

This PR changes what is connected to the SimpleSignal to only be a Qt signal. Thus, we're triggering update_display_of_axis_status to run in the Qt thread instead of running it in the asyncio loop thread. This is still inherently not thread safe, but will mitigate the chances of two threads trying to access the same memory space.

---

• Crated signal AxisControlWidget.requestDisplayRefresh.
• Removed AxisControlWidget.update_display_of_axis_status from its connection to Motor.signals.status_changed and movement_finished.
• Connected requestDisplayRefresh.emit to Motor.signals.status_changed and movement_finished.