mknode with array values, editorconfig, progress bar

[clbarnes]

mknode with array values

You can now create zarr arrays with given values like

just mknode path/to/my.zarr 3,2 uint8 --data 1,2,3,4,5,6

This is useful for creating transform test cases with path-form affines and rotations, coordinates, and displacements.

No extra dependencies because we already used zarr-python, which brings in numpy.

Supports scalar broadcasting (i.e. passing a single value to --data fills the array with that value). But that use case is probably better handled by setting the --fill-value, because then we don't need to write any chunks.

editorconfig

Standard configurations for JSON, markdown, TOML, YAML, so that more formatting can be consistently handled by editors rather than hitting pre-commit failures.

progress bar

oztest run can take a few seconds to gather the cases and run them, so by default a progress bar is now shown rather than leaving the user without visual feedback. Can be disabled with --no-progress/ -P.

The progress bar isn't very smooth, because at least with python dinguseses, the slowest part is the startup time of the dingus, which all happen in parallel, so it collects all the test cases very quickly, all the dinguses start up at the same time, then all of them complete at about the same time.

No extra dependencies because we already use rich for coloured terminal output.