[Dev] create tests for the plugin.

[Balvald]

I as the developer would like to have both unit tests and some other tests that simulate certain common and uncommon user behaviours that the plugin would need to face so that when I work on every next iteration of the plugin I don't have to do some tests manually and end up forgetting some obvious or important case and introduce new bugs into the project.

This one is free form no milestone attached to it. Though I've hinted I'll do this after v0.2.5 though probably will do atleast some of it during this.

• [Refactor] Move ArtemisScannerTracker class out of load.py into its own file. #41
• [Refactor] Move my own ui helper functions out of load.py into its own file. #42
• [Refactor] Move the eventhandling out of load.py into its own file. #43

Best would be also to introduce tests to prevent bugs from resurfacing so a list of bugs that need their tests on the other repo once its created:

• [BUG] Discrepancy between unsold scan value and vista genomics ui since Update 14.01 #12
• [BUG] if you reset a 2/3 scan, the "Distance to Scan #2:" field is not cleared. #32
• [BUG] "bug-ish": the third scan of a bio resets the "Distance to Scan 2" position to itself #37
• [BUG] in progress scan value (on the "Last Exobiology Scan:" line) always shows N/A now #35

[Balvald]

realized that to properly test this I'll need to be able to only import things that reacts on incoming events (the event handling region and stuff from the ArtemisScannerTracker class) without the getting the ui involved.

[Balvald]

slightly adjusted scope

[Balvald]

So far the thing is pretty bug free
(as in haven't seen me or anyone else experience any bugs again.)

I'll finally return to this sometime in August at the very least.