bad sketches dont block run

[cale-bradbury]

I had a sketch that was now failing due to the removal of THREE.GLTFLoader, that said, there could be any number of things that break a sketch.

This change continues with the initialization so you can at least load sketches that did init properly.

The sketch that failed does not appear in the list of sketches you can add.

This might leave an issue when opening a project that wants to use an uninitialized sketch due to bad changes, but I doubt it would break any worse than failing to init the three scene

[funwithtriangles]

Thanks for this, clearly an important topic that needed to be addressed. I was looking at the code and realised that it probably makes more sense to handle this at the lowest level possible, so that we're catching this when sketches are refreshed on code changes, not just when loaded on init.

I ended up in a little rabbit hole but I think the result is quite nice. We now explicitly return a Result object when importing sketches, with a success boolean flag. Functions higher up can decide what to do with that (e.g. later we'll want to do something with the UI to explain an error).

[funwithtriangles]

Because we're now checking for this issue lower down, other functions are affected. Here we're just not doing the reimport stuff if the module failed to load.

[cale-bradbury]

yeah, this looks really nice, feel free to merge :)