Avoid Duplicate Bots on Shared Futures Accounts

I note that when different Veles accounts are connected to the same exchange futures account, I must ensure bots trading the same coin and direction do not both operate on that shared account. Position locks only apply inside each API binding, so they won't prevent duplicate entries across separate bindings.

For example, if I have a BTC long bot in one cabinet, I should not run another BTC long bot from a different cabinet on the same futures account. I recommend centralizing or coordinating bot deployments, using a single API binding per strategy or manual checks to avoid conflicting positions and unintended margin exposure.