Eo-grow

- Fix pipeline-chain execution when using CLI

- Fixed `eogrow-validate` command when validating pipeline chains that use variables.
- Restricted version of `typing_extensions`

With this release we push `eo-grow` towards a more `ray` centered execution model.

- The local EOExecutor models with multiprocessing/multithreading have been removed. (Most) pipelines no longer have the `use_ray` and `workers` parameters. In order to run instances locally one has to set up a local cluster (via `ray start --head`). We included a `debug` parameter that uses `EOExecutor` instead of `RayExecutor` so that IDE breakpoints work in most pipelines.
- Pipeline chain configs have been adjusted. The user can now specify what kind of resources the main pipeline process would require. This also allows one to run pipelines entirely on worker instances.
- The `ray_worker_type` field was replaced with `worker_resources` that allows for precise resource request specifications.
- Fixed a but where CLI variables were not applied for config chains.
- Removed `TestPipeline` and the `eogrow-test` command.
- Some `ValueError` exceptions were changed to `TypeError`.

- Pipelines can request specific type of worker when run on a ray cluster with the `ray_worker_type` field.
- Area managers now generate the patch lists more efficiently.
- Pipelines have option to fail when temporally-ill defined EOPatches are encountered with the `raise_on_temporal_mismatch` flag.

- Fixed a bug in `BatchDownloadPipeline` where the evalscript was not read correctly.

- Pipelines can now save EOPatches in Zarr format
- Testing utilities now also compare vector-based files. Numerical precision of comparison was adjusted.
- Evalscripts are now read from storage. Removed import-path capabilities of config language.