manually update csvhelper to 25.0.0, fo-dicom to 4.0.7

[rkm]

Proposed Changes

Types of changes

What types of changes does your code introduce? Tick all that apply.

• Bugfix (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)
• Documentation-Only Update (if none of the other choices apply)
  • In this case, ensure that the message of the head commit from the source branch is prefixed with [skip ci]

Checklist

By opening this PR, I confirm that I have:

• Reviewed the contributing guidelines for this repository
• Ensured that the PR branch is in sync with the target branch (i.e. it is automatically merge-able)
• Updated any relevant API documentation
• Created or updated any tests if relevant
• Accurately updated the CHANGELOG
  • NOTE: This must include any changes to any of the following files: default.yaml, any of the RabbitMQ server configurations, GlobalOptions.cs
• Listed myself in the CONTRIBUTORS file 🚀
• Requested a review by one of the repository maintainers

Issues

[rkm]

Remaining failures caused by upstream BadMedicine DICOM lib

[rkm]

Need to bump this to 24.0.1

[rkm]

@jas88 I think we also need a release of BadMedicine.Dicom to bring-in the API updates

[jas88]

@jas88 I think we also need a release of BadMedicine.Dicom to bring-in the API updates

Good point - SMI/BadMedicine.Dicom#38 in the queue now