Refactor DICOM anonymizer to use Microsoft.Extensions.Configuration with strongly typed models

[Copilot]

This PR refactors the DICOM anonymizer to use the standard Microsoft.Extensions.Configuration framework with strongly typed models, eliminating the AnonymizerConfigurationManager and replacing dynamic JObject deserialization with compile-time type safety.

Key Changes

• Removed AnonymizerConfigurationManager
• Moved configuration loading logic directly into AnonymizerEngine constructors
• Engine now reads configuration files locally using Microsoft.Extensions.Configuration
• Replaced dynamic JObject deserialization with strongly typed models (AnonymizerRuleModel, PerturbSettings, DateShiftSettings, etc.)
• Enhanced configuration loading with multiple source support
• Renamed ConvertFromIConfiguration to ToAnonymizerConfiguration for better clarity

Benefits

• Type Safety: Compile-time validation and IntelliSense support
• Standards Compliance: Uses .NET's standard configuration system
• Maintainability: Eliminates reflection overhead and dynamic object access
• Backward Compatibility: Existing configuration files work unchanged

Validation

Manual testing confirms the anonymizer successfully processes DICOM files with the new configuration system while maintaining all existing functionality.

Fixes #256.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[jovinson-ms]

@copilot please restrict the changes to the DICOM project only. Please refactor the Anonymizer engine to read the configuration file locally using Microsoft.Extensions.Configuration, get rid of AnonymizerConfigurationManager, and update the files under /Rules to deserialize using models instead of using dynamic deserialization.

[Copilot]

@copilot please restrict the changes to the DICOM project only. Please refactor the Anonymizer engine to read the configuration file locally using Microsoft.Extensions.Configuration, get rid of Anonym...

I've completed the refactoring as requested. The changes are now restricted to the DICOM project only and implement all the requested improvements:

✅ Restricted to DICOM project only - Reverted all FHIR changes from previous commits
✅ Refactored Anonymizer engine - Uses Microsoft.Extensions.Configuration directly for local configuration file reading
✅ Removed AnonymizerConfigurationManager - Completely eliminated and moved functionality into AnonymizerEngine
✅ Updated Rules with strongly typed models - Replaced JObject deserialization with strongly typed models (AnonymizerRuleModel, PerturbSettings, DateShiftSettings, etc.)

The refactoring maintains full backward compatibility - existing configuration files work unchanged and the anonymizer successfully processes sample DICOM files. The solution now uses .NET's standard configuration system with compile-time type safety.

Commit: 4176041

[chrisribe]

@copilot function name ConvertFromIConfiguration is a bit vague. maybe "ToAnonymizerConfiguration"

[Copilot]

Renamed the method to ToAnonymizerConfiguration for better clarity. Commit: f441d91