Add volume object

overview

Add a Volume object to handle volume

need fix: volume/results should be a Nxdata and / or displaye dbu default from nabu reconstruction file

• provide API to save and load volumes
  • this should allow to keep as much as possible features of nabu's Writer
  • for now does not handle the case nabu wants to write a single slice to an edf file.
• add unit-test
• add documentation
• add tutorial
• add interface to allow compression when saving a volume to HDF5
• insure JP2K and Tiff file with pattern as any_prefix_{index_zfill4}.{extension} save in a folder with a name different than "any_prefix" can be loaded (this case can happen in nabu)
• for the HDF5Volume: insure data can be a VirtualLayout
• move the HDF5 to use the instead of the current format will be done in another PR if we want to do it
• add a util to load a slice only
• add management of file_prefix for single file volume
  • add more test on the file prefix usage
• [ ] add a util or an option to link different volume with an hdf5 master file this will be done in another PR in order to reduce and clarify code review.
• use urllib instead of reinventing the wheel...
• from this PR we should also be able to provide an url at nabu level and have a standalone at tomwer level which can provide something like:

tomwer volume-viewer url

and this should allow the display of the volume (through silx 3D view under it)

extra

close #49 (closed)

As this is a huge input and will break scan identifier this will be in a 1.0

url updated.

Here is a list on what looks url after the update (not file_prefix can be handled and it should ease adding more options like having different path for the data and metadata...):

scheme:tomo_type:path[?queries]

like:

tiff:volume:/tmp/pytest-of-payno/pytest-109/test_volume_with_prefix_TIFFVo0/acquisition/volume?file_prefix=test