Escape colon in XML names written by escaping XmlNameProcessors

[Sahana2524]

Colon passes through the escaping name processors

Base64NameProcessor counts a name holding a colon as already valid, and ReplaceNameProcessor keeps the colon in its allowed set, so a content-derived name such as a Map key "a:b" is written out verbatim. Output is namespace-aware, so that colon comes back as a prefix nothing declares and the document no longer reads: <DTO><badMap><a:b>v</a:b></badMap></DTO> fails with Undeclared namespace prefix "a", while "a:b:c" and ":leading" do not even parse. That round trip is what these two processors are there to protect, and newAlwaysOnBase64Processor() already handles the same keys cleanly, so the colon looks like an oversight in the allowed sets rather than a deliberate exception.

Dropping it means such names get escaped (base64, still a lossless round trip) or replaced instead. Only encodeName changes: decodeName keys off the prefix for base64 and is a no-op for replacement, so names coming from a non-namespace-aware parser are still passed through untouched. Covered by round-trip tests in XmlNameEscapeTest; the rest of the suite is unchanged.

[github-actions]

🧪 Code Coverage Report

Metric	Coverage	Change
Instructions	77.69%	📈 +0.000%
Branches	70.97%	📈 +0.000%

Coverage data generated from JaCoCo test results