Support of all UTF-16 characters in IdWithWildcardsNetworkElementIdentifier

[olperr1]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem?

No

What kind of change does this PR introduce?

Feature

Does this PR introduce a new Powsybl Action implying to be implemented in simulators or pypowsybl?

• Yes, the corresponding issue is here
• No

What is the current behavior?

• The only allowed characters in the IdWithWildcardsNetworkElementIdentifier pattern were from A to Z (capitalized or not), the digits, '_', '.' or '-'.
• The wildcard was '?'.

What is the new behavior (if this is a feature change)?

• All the UTF-16 characters are allowed in the pattern.
• By default, the wildcard is '?', but the user can change this character if needed / wanted.

Does this PR introduce a breaking change or deprecate an API?

• Yes
• No

If yes, please check if the following requirements are fulfilled

• The Breaking Change or Deprecated label has been added
• The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

• The JSON serialization of IdWithWildcardsNetworkElementIdentifier now contains a wildcard attribute. When reading a JSON without this attribute, the default wildcard (?) is used.
• As a consequence, the serializations of the following elements (which can contain a IdWithWildcardsNetworkElementIdentifier) are potentially impacted. Their serialization version numbers were increased:

Category	Element	Previous version	New version
Action list	ActionList	1.1	1.2
Contingency list	IdentifierContingencyList	1.2	1.3
Contingency list	ListOfContingencyLists	1.0	1.1

⚠️ The JSON serialized version of these elements (action or contingency list) may be not readable with older versions of PowSyBl.

Also, this change of serialization versions can have an impact on your unit tests (if you use a JSON serialized object as a reference).

Other information:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
86.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud