This PR brings active/passive modes for parent coins which aims to keep children token states in memory when disable_coin is executed for parent coin.

Progress:

• adding is_available atomic flag, is_available and update_is_available to coins context.
• using is_available and update_is_available on certain conditions around coin activations and disable_coin.
• when parent coin is passived(disabled while having active tokens), only update is_available to true on re-activation.
• implement force_disable_all RPC to drop everything on target coin. add force_disable flag to disable_coin RPC
• update related tests like mm2_test_helpers::for_tests::disable_coin_err
• add unit and integration tests for testing this implementation
• return passivized flag on disable_coin RPC response

Breaking Changes:

dependent_tokens is removed from the RPC response. Because we no longer care about if there are active tokens or not.

--

Docs for GUI:

cc @yurii-khi @KomodoPlatform/qa

• new param force_disable: bool(false as default) for disable_coin RPC request payload

• • When this is not true, if platform has tokens enabled, disable_coin will passive the platform coin with keeping all the tokens active and usable. When force_disable is true, no matter if platform passive, or active, it will be disabled with all it's tokens.

• new field passivized on disable_coin RPC response

• • This is only true if requested coin was passivized. This can be useful for showing the passivized coin with different color on GUI side(maybe even let user to force_disable passivized coins to disable all tokens and drop swaps which is faster in terms of UX)

When passive coin is re-activated, it only changes it's passive status(and activates the tokens if enabled with tokens) without updating the other fields like rpc urls, tx history, etc. If these fields needs to be changed, the coin must be disabled with force_disable flag which cleans up the memory from that platform.

--

Resolves #1641