Add ty for CI Type Checking

[Grochocinski]

Fixes #179

The two main fast type-checkers for Python at the moment are ty and Pyrefly, although both are still quite early in development. While searching for comparisons between the two, I found this interesting article on the subject that compares their advantages/disadvantages as well as diving into each type checker's approach to type resolution. Highly recommend reading it.

I ended up selecting ty for type checking since it's made by Astral (the developers of the Ruff linter/formatter, which we already use, and the uv package manager, which our project is compatible with and I personally use. I've had great experiences with all of Astral's products and from my experiences so far with ty, I believe it will continue that trend. Additionally, after reading the linked article above, I think ty's more forgiving inferred typing and significantly clearer error messages will be advantageous when trying to type current-untyped existing classes such as the GUIs.

Since this PR is just for the action itself, the typing errors will need to be addressed at a later time. This would be the case regardless of which type-checker we got with.

[Grochocinski]

had to rebase/force-push to sort out a merge conflict, branch-specific commits remain unchanged.

[Grochocinski]

I adjusted the exclude list to individually list all failing files with the expectation that:

1. No additional files will be added to this list (under normal circumstances)
2. Work will be performed to fix any issues ty is flagging in these files, at which point they will be removed from the exclude list

This essentially just modifies the behavior of the ty action to pass for now while we work on fixing the typing backlog we now have.