More robust CI setup for publishing

[Jakub Arnold]

I'll just leave this as partly an open discussion. Comfy is my first workspace crate that I'm publishing, and even tho I have a few smaller ones (e.g. grids and blobs) I feel like the current setup for publishing comfy versions isn't exactly the best.

While I'd like to avoid a huge process around making any kind of change, doing manual version bumps in three crates and editing all dependencies and publishing them all by one and checking that they build and tests run ... is well error prone, I already made a few mistakes :)

If anyone has a good idea for how to make this process a bit more automated I'd be very happy to hear it. I'm not sure how other big engines (e.g. bevy) do this, but I'm also not sure if what they do is even transferrable to a tiny crate like comfy.

There's already a few issues I'm running into, e.g. the physics example requires a feature flag blobs, and I just ended up hardcoding this in all my scripts, etc. etc.

Anyway, very much open to suggestions on the whole setup.