Enable retrieving and overriding wind attack angle

[ai-qui]

Please check if the PR fulfills these requirements

• 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?

fixes #101

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)

Following parameters and attributes are renamed to better reflect what their signification:
azimuth -> cable_azimuth
wind_angle -> wind_azimuth
attack_angle -> wind_attack_angle

The parameters' order used to instantiate ConvectiveCooling has been changed and a new optional parameter wind_attack_angle has been added. Parameter wind_azimuth is now optional. Please adapt your code if you use positional argument. No changes are required if you use keyword arguments.

For cigre model:

# Before
ConvectiveCooling(
    altitude,
    azimuth,
    ambient_temperature,
    wind_speed,
    wind_angle,
    outer_diameter,
    roughness_ratio,
    g,
    ...
)

# After
ConvectiveCooling(
    altitude,
    cable_azimuth,
    ambient_temperature,
    wind_speed,
    outer_diameter,
    roughness_ratio,
    wind_azimuth,
    wind_attack_angle,
    g,
    ...
)

For IEEE, olla and RTE models:

# Before
ConvectiveCooling(
    altitude,
    azimuth,
    ambient_temperature,
    wind_speed,
    wind_angle,
    outer_diameter,
    ...
)

# After
ConvectiveCooling(
    altitude,
    cable_azimuth,
    ambient_temperature,
    wind_speed,
    outer_diameter,
    wind_azimuth,
    wind_attack_angle,
    ...
)

[sonarqubecloud]

Quality Gate failed

Failed conditions
64.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[ai-qui]

SonarCloud analysis fails because all the code where parameters/variables have been renamed is considered "new" and sonar complains about insufficient test coverage. I suggest bypassing the condition on new code test coverage for this PR since adding tests isn't in this PR's scope.

[ai-qui]

TODO: test that attack angle is always between 0 and 90°