Depend on unigen crate - scope to render only

[selfup]

Big changes! Will think about this for a few days to make sure this is the path forward.

In theory, unigen-rs will be easier to work on.

This will allow us to keep the renderer (oxidizy) scoped to only rendering and not having to deal with dependency and source code conflicts once development kicks back in for a deep dive in the universe generator.

There is also the chance that we will need to do GPU compute in unigen and this might conflict with the renderer pipeline. That or we delegate GPU compute to bevy somehow. It's all very exciting either way.

[selfup]

For further clarification: unigen-rs is this repo with all the history, but newly scoped to just the unigen crate logic we all worked on. Now this repo will also keep all of the history but scope down to just visualizing the universe. One is the data producer and the other is the data consumer.

[whereswald0]

For further clarification: oxidizy-rs is this repo with all the history, but newly scoped to just the unigen crate logic we all worked on. Now this repo will also keep all of the history but scope down to just visualizing the universe. One is the data producer and the other is the data consumer.

This does make more sense to split the two off into their respective repos. After the split, I'm assuming not much future work will occur in the oxidizy repo, right?

[selfup]

I'll keep it up to date with bevy engine but as our data gets more and more complex it should just stay high level (visualizing atoms) from a rendering perspective. I'd imagine after a while, as we rely on GPU compute, large visualizations will compete with VRAM.

[selfup]

Updated deps. All good to go

[selfup]

Woohoo 🎉