Prepare for and hold a 4th pyright/Ruff correction day

As a developer working on IBEX I want to continue to clear out and correct the legacy pyright/ruff errors that are in the system now that we have instigated these checks as standard so that small/urgent changes don't lead to lots of fixing. This will follow on and add to the work of [#8742](https://github.com/ISISComputingGroup/IBEX/issues/8742).

## Acceptance Criteria:
- [x] Identify a day that the majority of the group are free and available and book it in the calendars
- [ ] Everyone who can spends as much time as they can on this day fixing these issues
- [ ] Open tasks from previous pyright ticket are continued
- [ ] The named person on this ticket provides a breakdown of the work needed (including carried over) to facilitate the team undertaking the task (this has to be done before the day is held). https://github.com/ISISComputingGroup/IBEX/issues/8742 can be used as a starting point. The breakdown should make it possible to see at a glance who is working on what and to track PRs and completion of work.
- [ ] If required, a follow up ticket for remaining work is created