[WIP] Parameters improvements

[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

What is the current behavior?

What is the new behavior (if this is a feature change)?
The parameters now have new optional attributes:

• categoryKey: a free-text attribute containing a business key to group together the parameters which concern a same topic;
• usageRestrictions: an object indicating that the current parameter is used only when another parameters have a specific value. For instance, parameter p3 is used only when p1 have a value in { "value1", "value3"} AND p2 is true;
• unitSymbol: a free-text attribute containing the unit of the expected values for the parameter. The most common units can be found in ParameterUnit.

To ease the parameters' creation, a builder was also introduced, but the existing methods were kept.

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)

• Parameter.getPossibleValues() now returns an Optional<List<Object>> instead of a nullable List<Object>.
• LoadFlowProvider implementation should implement the new method:
  • List<String> getUnsupportedGenericParameters();, which returns the ids of the generic parameters which are unsupported by the LoadFlow provider.

Other information:

For instance, you can create parameters with the given syntaxes:

// Old syntax: direct use of the constructor
Parameter param1 = new Parameter(key1, ParameterType.STRING, "a 1st param", "a", List.of("a", "b", "c"));

// New syntax: via the builder
Parameter param2 = Parameter.builder(key2, ParameterType.BOOLEAN, "a 2nd param", Boolean.FALSE)
        .withCategoryKey("Category")
        .build();

// Create a parameter depending on the values of param1 and param2
Parameter param3 = Parameter.builder(key3, ParameterType.STRING, "", "yes")
        .newUsageRestriction()
            .withRestriction(key1, Set.of("b", "c"))
            .withRestriction(key2, Boolean.FALSE)
        .add()
        .withCategoryKey("Category")
        .build();

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarCloud

[olperr1]

This PR was revert to draft as it needs to be reworked.