Bump IIDM to 1.17

[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)
• A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?

No

What kind of change does this PR introduce?

Feature

What is the current behavior?

IIDM is in version 1.16.

What is the new behavior (if this is a feature change)?
IIDM is in version 1.17.

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)

Downstream projects should:

• Check in their versionable extensions' serializers/deserializers (classes extending AbstractVersionableNetworkExtensionSerDe) that a SerDeVersion value support the new version (1.17) (usually, at least a SerDeVersion has its maxIidmVersionExcluded attribute set to null);

• Upgrade the version in their XIIDM / JIIDM unit test files corresponding to the current version:

  • For ".xiidm" or ".xml" files: replace:

    • xmlns:iidm="http://www.powsybl.org/schema/iidm/1_16" with xmlns:iidm="http://www.powsybl.org/schema/iidm/1_17";
    • xmlns:iidm="http://www.powsybl.org/schema/iidm/equipment/1_16" with xmlns:iidm="http://www.powsybl.org/schema/iidm/equipment/1_17";

  • For ".json" or ".jiidm" files: replace "version" : "1.16" with "version" : "1.17".

Other information:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud