Restructure into a cargo workspace

[EriKWDev]

By restructuring a bit we could create a cargo workspace so that we could separate the different headers into their own crates, or at least separate the imgui header bindings into its own crate since it requires the cimgui dependency which everyone might not need/want.

This would also make it much easier to create some manual projects such as an egui https://github.com/emilk/egui renderer for sokol that could still be hosted in the same git repo here.

[floooh]

I'll need to tinker with the bindings a bit and read up on cargo workspaces before having an opinion on that :)

[EriKWDev]

Of course :)

Here are some examples of other projects that are structured as cargo workspaces:

• https://github.com/EmbarkStudios/puffin
• https://github.com/code-disaster/sokol-rs
• https://github.com/helix-editor/helix
• https://github.com/emilk/egui

The benefit is that you can have a single repository with all the related code but still publish multiple separate crates that can be depended upon and compiled independently.

The alternative is to keep the structure as is.

I think it's mostly a preference thing, but I noticed that if you add this GitHub link as a dependency in cargo, cargo will download all the cimgui/imgui stuff wether you wanted it or not during compilation which might be avoidable if we split into a workspace, but that would have to be verified.