feat: New Omni Booter

[bgroupe]

This PR adds:

1. A tweaked omni_boot.py designed to be run using the Ray Jobs CLI, ie ray job submit --runtime-env omni_env.yaml --submission-id omni01 -- python omni_boot.py
2. A dataclass that wraps the jetstream data to conform to the shape the processors expect
3. New actor config to make them immortal
4. New settings classes to control the behavior of the booter, the SQS consumer and the streamer
5. New utils for reconciling actors across a Ray Cluster

[bgroupe]

@DGaffney So I noticed that there is a strict actor dependency tree that is not currently enforced, ie you can start them out of order and they will boot but they take empty lists in their constructors and will be DOA the minute they try to use the dispatcher. I added this flag to throw exceptions when the list comes back empty. I also expanded search to include all namespaces, since you can set the namespace as an env var now (defaults to main). This would be useful if you wanted to run heterogenous actors like as a/b experiments or something.

[bgroupe]

this is pretty helpful since this is the parent rescue in long chain of async child tasks, but I'm not married to leaving it here if we wanna remove.

[bgroupe]

@DGaffney I actually have a submodule with just this jetstream and a slimmed down build, since it doesn't need any of the heavy grazer dependencies. But I haven't pushed it yet because I was curious if this would get replaced at some point by jetstream-turbo?