[ENH]: Use junifer-data datalad dataset for fetching data

[synchon]

• description of feature/fix
• tests added/passed
• add an entry for the latest changes

This PR adapts junifer-data datalad dataset at https://github.com/juaml/junifer-data to provide data for junifer.

[github-actions]

PR Preview Action v1.6.0
🚀 View preview at https://juaml.github.io/junifer/pr-preview/pr-418/
Built to branch gh-pages at 2025-01-24 17:22 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.01%. Comparing base (b8459c8) to head (16c1a16).
Report is 1 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff           @@
##            main    #418    +/-   ##
======================================
  Coverage   0.01%   0.01%            
======================================
  Files        133     133            
  Lines       5764    5498   -266     
======================================
  Hits           1       1            
+ Misses      5763    5497   -266     

Flag	Coverage Δ
docs	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
junifer/data/coordinates/_coordinates.py	0.00% <ø> (ø)
junifer/data/masks/_masks.py	0.00% <ø> (ø)
junifer/data/parcellations/_parcellations.py	0.00% <ø> (ø)
junifer/data/template_spaces.py	0.00% <ø> (ø)
junifer/data/utils.py	0.00% <ø> (ø)

[fraimondo]

This function needs to check that we are also using/cloning the exact junifer data version that we want.

In our last discussion, we said we will have a subdirectory inside the junifer_data with the corresponding version to be used with the currently running junifer version.

So somewhere in junifer code, we will have a JUNIFER_DATA_VERSION variable with a string/number/id.

Then we will look if the directory junifer_data/{JUNIFER_DATA_VERSION} exists, that its a datalad dataset, it's clean and its tag corresponds to JUNIFER_DATA_VERSION.

This way we can keep junifer data for several installed junifer versions, each one consistently using the data.

[synchon]

This PR is part of that migration and serves to move manual inconsistent asset downloads to using junifer-data via datalad. The idea is to move all dataset validating and data fetching machinery to https://github.com/juaml/junifer-data-client and junifer using its API to fetch data as required using the technique you described. v1.0.0 image of junifer-data is being built and will be published soon.

The next PR will adapt the usage of junifer-data-client API while taking care of versions.

[synchon]

Needs to go before #363