Add activation_price support for trailing stop orders

[hope2see]

Pull Request

• Introduce the activation concept to trailing stop orders by adding the activation_price attribute, a feature already supported by advanced exchanges such as Binance, OKX, and others.
• Resolves Issue2573
• Related with Issue2523

Type of change

Delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• [v] New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [v] This change requires a documentation update

How has this change been tested?

Describe how this code was/is tested.

• All existing tests passed : pytest, pre-commit
• Updated 2 existing unit tests to include the activation_price attribute. (test_exchange_trailing_stops.py)
• Added 4 new tests for the extended features. (test_exchange_trailing_stops.py)

[cjdsellers]

Hi @hope2see

Thank you for the contribution!

Very initial skim looks good, I'll do a proper review tomorrow.

[cjdsellers]

Hi @hope2see

Thanks for your patience.

This is well-implemented and tested. I'll make some minor tweaks after merge, which won't affect the core behavior.

Could you add tests for str() and repr() for trailing stop orders, with and without the activation price? Since we're introducing the optional -ACTIVATION component, these can help catch formatting issues with commas or whitespace.

Many thanks again for this valuable contribution! 🙏

[cjdsellers]

@hope2see

Another valuable follow-up would be implementing this on the Rust side as well. Even if its just the activation_price parameter for the trailing stop orders, although the full implementation and testing would be the most ideal.

I understand if you're not comfortable enough with Rust, or don't have the bandwidth if implementing for the production code meets your needs currently. But if you did want to become involved there too, this would be a great entry point.

[hope2see]

@cjdsellers
Thank you for this quick merge and kind suggestion.

Could you add tests for str() and repr() for trailing stop orders, with and without the activation price?
No problem with adding this. :)

As for the Rust-side implementation, I would like to contribute, but I’m currently tied up with other work and don’t have much experience with Rust yet. So I think it would be better handled by someone else.