getSpecificParameters methods for analyses providers

[olperr1]

Describe the current behavior

The following providers have methods allowing to retrieve the specific parameters' description:

• LoadFlowProvider
• ShortCircuitAnalysisProvider

Describe the expected behavior

The other providers could also expose methods allowing to retrieve this description:

• SecurityAnalysisProvider
• SensitivityAnalysisProvider

And maybe:

• DynamicSecurityAnalysisProvider
• DynamicSimulationProvider

(These need to be checked.)

Describe the motivation

For now, the motivation is only to have consistency between the providers.

Extra Information

The methods to add are:

• List<Parameter> getSpecificParameters()
• List<Parameter> getSpecificParameters(PlatformConfig platformConfigConfig)

[antoinebhs]

I was thinking of a common interface for computation providers to avoid similar problems in the future. There is a lot in common but also some differences:

	SensitivityAnalysisProvider	SecurityAnalysisProvider	DynamicSecurityAnalysisProvider	DynamicSimulationProvider	LoadFlowProvider	ShortCircuitAnalysisProvider
Common methods	findAll	findAll	findAll	findAll	findAll	findAll
	run	run	run	run	run	run
Common to most provider methods	getSpecificParametersSerializer	getSpecificParametersSerializer	getSpecificParametersSerializer		getSpecificParametersSerializer	getSpecificParametersSerializer
	loadSpecificParameters	loadSpecificParameters	loadSpecificParameters		loadSpecificParameters	loadSpecificParameters
	loadSpecificParameters	loadSpecificParameters	loadSpecificParameters		loadSpecificParameters	loadSpecificParameters
	updateSpecificParameters	updateSpecificParameters	updateSpecificParameters		updateSpecificParameters	updateSpecificParameters
Should be common to providers					getModuleConfig	getModuleConfig
					getSpecificParameters	getSpecificParameters
					getSpecificParameters	getSpecificParameters
Specific methods	getSpecificParametersNames	getSpecificParametersNames	getSpecificParametersNames		createMapFromSpecificParameters
	getLoadFlowProviderName	getLoadFlowProviderName	getDynamicSimulationProviderName		getSpecificParametersClass

Giving this, I would suggest a common interface for all computation providers mentioned (SpecificParametersProvider?) to also add other missing methods.
It would include:

• getSpecificParametersSerializer
• loadSpecificParameters
• loadSpecificParameters
• updateSpecificParameters
• getModuleConfig
• getSpecificParameters
• getSpecificParameters

and it looks like we often either need the class or name for specific parameters but I haven't checked where these methods are used/if it's meaningful for all providers:

• getSpecificParametersClass
• getSpecificParametersNames

It would make the code more consistent for all the providers.