feature: Returns just dictionary when loading .topostats

[ns-rse]

Closes #109

Rather than return the HDF5 object loaded from .topostats as a dictionary as the third item in a tuple along with the
image and pixel_to_nm_scaling (both of which are extracted from the loaded data anyway) just the dictionary is
returned. This matches the structure of objects created by TopoStats and how they are saved to HDF5 files.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.58%. Comparing base (ac9753c) to head (0fb1dbd).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #112      +/-   ##
==========================================
- Coverage   74.62%   74.58%   -0.05%     
==========================================
  Files           8        8              
  Lines         607      606       -1     
==========================================
- Hits          453      452       -1     
  Misses        154      154              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[SylviaWhittle]

Not tested locally but fail to see what could break here.

Must remember that when a PyPI release is made, in TopoStats, to require AFMReader's version to be at least that one, since TopoStats will expect a single dictionary instead of a tuple. A little bit of a headache with changing TopoStats and AFMReader's interoperability ^^;

[ns-rse]

Thanks @SylviaWhittle for the review and approval 👍

Must remember that when a PyPI release is made, in TopoStats, to require AFMReader's version to be at least that one, since TopoStats will expect a single dictionary instead of a tuple. A little bit of a headache with changing TopoStats and AFMReader's interoperability ^^;

Yeah, I was trying to think how to handle that, its ok on development and once a release is made of both but if people explicitly install an older version of TopoStats that pulls in the newer version of AFMReader that won't work (might arise if pip uses cached packages so we should perhaps update documentation to include --no-cache-dir advice when using pip install and make it really prominent on the README.md as well as the website.

I'll look into whether its possible to add warnings about this, perhaps to a new release of AFMReader to the tune of This only works with TopoStats >= 2.x.x if you are using an older version you will have to manually downgrade AFMReader using pip install AFMReader==0.0.4 or similar as we can't modify already released versions of TopoStats to provide such a warning.

[ns-rse]

I've written up what might need updating/changing in TopoStats # 1086.