Electron Port

[l0go]

Kinda messy, just like it should be!

My main rationale is that the current nwjs version doesn't run on my Chromebook, plus it is just overall clumsy. Electron gives us some neat stuff that we can implement later, like installers and automatic updating. Structurally Electron is separated into two pieces: a main process and a renderer process. Ideally the sys/node calls are all separated into the main process, but we still have some stuff in the renderer. Instead of dealing with the incredible structural burden (patching asys stuff into very recursive sync code isn't fun) though, I am just gonna wait for the inevitable HaxeUI rewrite.

I think this is basically complete? I probably missed something obvious, but it looks like the sample works as intended. If anyone can test this, particularly on macOS and Windows, it would be appreciated!

Things that should be considered after merging (and should probably be separate issues):

• Stop vendoring CastleDB. We have a few small patches that need to be either upstreamed or moved, shouldn't be too hard?
• Rebranding? @dazKind proposed either Bastion or Citadel. Seems like there is a bit more collision with the former, so I am in favor of Citadel. Oh, also I don't think GitHub indexes forks? I think the only way to fix this is to make a new repo or contact GitHub support.
• Packaging: Electron has a thing called Forge, seems to be some sort of build system? Might be worth looking into.
• Implementing Blockchain, AI, and advertising functionality to make the shareholders happy /s