Fix ConsentInterceptor destroying sibling entries in repeating fields (e.g. contained) when replacing a resource

[jkiddo]

This pull request addresses an important bug (#8212) in the ConsentInterceptor related to handling resources in repeating fields (such as contained) when processed by an IConsentService. Previously, replacing a resource in a repeating field could inadvertently remove all sibling entries, but this is now fixed. The changes also add comprehensive tests to ensure correct behavior and document the fix.

Bug fix for replacing resources in repeating fields:

• Updated IMutator interface and its implementations (BaseRuntimeDeclaredChildDefinition, RuntimeChildExt) to add a replace method that swaps only the targeted entry in a repeating field, instead of clearing the entire list. [1] [2] [3]
• Modified ConsentInterceptor to use the new replace method instead of setValue, ensuring that only the intended resource is replaced and sibling entries remain unaffected.

Testing and documentation:

• Added new tests in ConsentInterceptorTest to verify that all contained resources survive when unchanged and that replacements occur in place without disturbing sibling entries. [1] [2] [3] [4]
• Added a changelog entry describing the bug and its resolution.

[tadgh]

Formatting check succeeded!