Add a new parameter to control if the connection constraint should be written in the highest or lowest resolution per connection

[datejada]

The current code includes a global parameter: use_highest_resolution_constraint_ratio_out_in_connection_flow, which determines whether the connection constraints are written at the highest or lowest resolution. The default setting for this parameter is true.

However, there are situations where users may want to specify different resolutions for different connection types. For example, they might prefer the highest resolution for electricity connections while opting for the lowest resolution for gas connections. In these cases, the global parameter can be too restrictive.

To address this issue, we propose creating a new parameter, use_highest_resolution_constraint_ratio_out_in_connection_flow, that is specific to the connection__node__node relationship. This new parameter would allow users to override the global setting. If the parameter is defined at the relationship level, it will use that value; if it is not defined, the code will revert to the global parameter's current setting.

After finishing the changes, remember to:

• Update the documentation
• Update the test to cover the case in which the parameter definition in the relationship overwrites the global value of the parameter.

Please feel free to add or modify this issue: @DillonJ
Assigning it to @aporrasc for pair programming training