fix(XMLPatch): support multiple sibling elements in replace operations

[louga31]

Summary

• ApplyReplace used replaceElement.Element(targetName) which only returns the first matching child element, silently dropping any additional siblings
• Fixed to insert all child elements from the <replace> operation, preserving their order
• Added logging to indicate when multiple siblings are inserted (e.g. "and 3 sibling(s)")

Problem

When a <replace> diff operation contains multiple sibling elements:

<replace sel="path/to/do_if[@value='...']">
  <do_if value="...">...</do_if>
  <do_elseif value="...">...</do_elseif>
  <do_elseif value="...">...</do_elseif>
</replace>

Only the first <do_if> was inserted — the <do_elseif> elements were silently dropped. This is a valid pattern in X4 diff patches where a single element is replaced with an if/elseif chain.

Fix

Instead of replaceElement.Element(targetName) (single element), the fix uses replaceElement.Elements().ToList() to collect all children, then inserts them in order using AddAfterSelf before removing the original target.

Test plan

• Verified with X4 diff patches containing multi-sibling <replace> operations
• Single-element replacements continue to work as before
• Attribute and text node replacements are unaffected

[chemodun]

Thanks. But excuse me, in parallel several day ago made appropriate patch for the both utils.
Currently have possibility to publish it.

One more time thank and excuse.