Decide on UI solution

[SK83RJOSH]

Currently jc2_tools uses bevy inspect + bevy egui for it's UI... which is fine, but far from optimal for building anything particularly complex. This is the main pain point to extending the app right now, as I would like to use a reactive framework of some kind, or at least, something that allows me to iterate without rebuilding the app repeatedly.

In another project, I have managed to wrap slint and get it rendering offscreen. It would be an excellent solution in terms of productivity, but would require writing some additional bevy glue code to handle input / rendering to the main bevy window. Additionally, while it works in the other project, it's unfortunately very slow to read back data from the GPU as one might expect. Perhaps OK for this project given it only needs to be real time, and isn't doing anything terribly complex rendering wise.

An alternative solution may be to use bevy_reactor, though productivity issues would still remain given there's no editor or hot reloading... but it's at least far more flexible and feature complete than egui and reactive.