fix failing CIL unit tests and Gadgetron/ISMRMRD HDF5 linking error

[paskino]

Changes in this pull request

• fixes Fix failing CIL unittests #987
• closes CI: docker tests fail because Gadgetron is not running #991

Testing performed

Related issues

Checklist before requesting a review

• I have performed a self-review of my code
• I have added docstrings/doxygen in line with the guidance in the developer guide
• I have implemented unit tests that cover any new or modified functionality
• The code builds and runs on my machine
• CHANGES.md has been updated with any functionality change

Contribution Notes

Please read and adhere to the contribution guidelines.

Please tick the following:

• The content of this Pull Request (the Contribution) is intentionally submitted for inclusion in SIRF-SuperBuild (the Work) under the terms and conditions of the Apache-2.0 License.

[paskino]

The residual error in the DEVEL_BUILD is TORCH_TEST_PYTHON

https://github.com/SyneRBI/SIRF-SuperBuild/actions/runs/23851867425/job/69533945161?pr=989#step:14:1066

[KrisThielemans]

It's strange that we don't get any output that says what the failure. we just have

CoverageWarning: Module sirf.torch was never imported. (module-not-imported); 

but that could be irrelevant, as the coverage stuff is broken since a few years.

On the other hand, this is the DEVEL_BUILD=OFF build (with g++11), while all others are fine. So, I wonder if we shouldn't be updating the SIRF_TAG.

[paskino]

No, that's the DEVEL_BUILD=ON

So currently

DEVEL_BUILD	SIRF_TAG	Note
OFF	11a6a50fc13bf52439d0c1ec15ebacfbadada8c5	29/1/26, before #1305
ON	master	after #1305

This means that only the DEVEL_BUILD=ON has the code merged from SyneRBI/SIRF#1305 and runs the relative unit tests, which fail.

It also means that indeed we need to change the SIRF_TAG to nearly master, or whatever commit we want to tag as v3.10.0.

[KrisThielemans]

That's what I meant... Good luck!

[casperdcl]

we'll tackle #992 separately