Added support for different configurations per SO level

[mrcrdwd]

Allow for using the same activation-percentage but with different settings per so-level.

The use case is when you, for instance, want to tighten the band between your take profit and stop loss when you take on more so levels.

The configuration below is now supported.

{"activation-percentage": "3.0","initial-stoploss-percentage": "-1.0","sl-timeout": "30","activation-so-count": "1","sl-increment-factor": "1.0","tp-increment-factor": "0.7"},
{"activation-percentage": "4.0","initial-stoploss-percentage": "-1.0","sl-timeout": "30","activation-so-count": "0","sl-increment-factor": "1.0","tp-increment-factor": "0.7"},
{"activation-percentage": "4.0","initial-stoploss-percentage": "-1.0","sl-timeout": "30","activation-so-count": "1","sl-increment-factor": "1.0","tp-increment-factor": "0.7"},

The script will use the LAST configuration entry that matches the current profit and so level conditions.

Example

• With a profit of 2.5% and SO level 0, nothing happens.
• With a profit of 3.5% and SO level 0, nothing happens.
• With a profit of 4.5% and SO level 0, the second config rule gets applied.
• With a profit of 3.5% and SO level 1, the first config rule gets applied.
• With a profit of 4.5% and SO level 1, the third config rule gets applied.

The activation-percentage must be specified in an ascending order and so-count must also be specified in an descending order.

[mrcrdwd]

In hindsight, this could be improved even further by checking the max activation-percentage that matches the current profit. That way the order in the config file would be less important and less error-prone.