Refactor Python and Orthanc Dockerfiles

[jeremyestein]

Description

Fixes #{issue_number}:

A cut down version of #400 , with just the Dockerfile de-duping. If we decide #400 is too risky to merge now, we can at least merge this one and do the rest of #400 later. The advantage is it enables further work on the Dockerfiles, such as switching to uv.

Type of change

Please delete options accordingly to the description.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Suggested Checklist

• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have commented my code, particularly in hard-to-understand areas.
• I have passed on my local host device. (see further details at the CONTRIBUTING document)
• Make sure your branch is up-to-date with main branch. See CONTRIBUTING for a general example to syncronise your branch with the main branch.
• I have requested review to this PR.
• I have addressed and marked as resolved all the review comments in my PR.
• Finally, I have selected squash and merge

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.17%. Comparing base (6435ebb) to head (98fa689).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #583      +/-   ##
==========================================
- Coverage   87.38%   85.17%   -2.22%     
==========================================
  Files          76       72       -4     
  Lines        3386     3116     -270     
==========================================
- Hits         2959     2654     -305     
- Misses        427      462      +35     

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

[p-j-smith]

looking really nice - just a question around downloading the DICOM spec for Orthanc Anon

[p-j-smith]

downloading the Python spec is pretty slow to do, so I think ideally this would be one of the earlier layers in the image. Not sure the best way to do that? Either include it in Raw, or have separate Raw and Anon images?

[stefpiatek]

Looks good, will leave it to you and Paul to work out the best way to have the python spec downloaded and cached