Add XMLLiteral well-formedness helper to Lyo

[jadelkhoury]

Signed-off-by: Jad El-khoury jad.el.khoury@scania.com

Description

Add XMLLiteral well-formedness helper to Lyo

Checklist

• This PR adds an entry to the CHANGELOG. See https://keepachangelog.com/en/1.0.0/ for instructions. Minor edits are exempt.
• This PR was tested on at least one Lyo OSLC server or adds unit/integration tests.
• This PR does NOT break the API

[berezovskyi]

Should be safe to add to Lyo 4.1.

Note that if users manually edit XML and use rdf:datatype instead of rdf:parseType, you need to unescape the string before the check: https://commons.apache.org/proper/commons-lang/apidocs/org/apache/commons/lang3/StringEscapeUtils.html#unescapeXml-java.lang.String-. This was not added to the code because this situation can only arise if you are editing RDF/XML by hand,

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

0.0% Coverage
0.0% Duplication

[berezovskyi]

@jadelkhoury I am targeting this PR for Lyo 5.1 unless you have a good reason not to do that.

[Jad-el-khoury]

Sounds good to me. Is tehre a reason we kept it open for so long? is it safe to merge now?

[berezovskyi]

I think it was connected to #214, which may not be as safe to merge as this helper.

The main reason for the delay is that this helper is mainly useful for Jazz applications that misuse the XMLLiteral type to return what should be a regular strings and I don't deal with these Jazz quirks daily. And so it fell off my radar.

Tests passed on all JDKs, merging.