Use subscribe flag to get and put contract requests

[netsirius]

This pull request introduces a new subscribe field to various contract operations, ensuring that the subscription status is consistently handled throughout the codebase. The changes span multiple files and functions, adding the subscribe field where necessary and updating function calls and state management accordingly.

Key changes include:

Addition of subscribe field:

• Updated the start_op function in crates/core/src/operations/get.rs to include the subscribe parameter.
• Modified the GetState enum in crates/core/src/operations/get.rs to include the subscribe field in relevant states. [1] [2]
• Added the subscribe field to various function calls and state initializations in crates/core/src/client_events.rs and crates/core/src/contract/executor.rs. [1] [2] [3] [4] [5] [6] [7] [8] [9]

Consistent handling of subscribe in operations:

• Ensured the subscribe field is correctly passed and utilized in the GetOp and PutOp operations. [1] [2] [3] [4] [5] [6]
• Updated test cases in crates/core/src/client_events.rs to include the subscribe field. [1] [2] [3]

Subscription request handling:

• Modified subscription request logic in crates/core/src/node.rs and crates/core/src/operations.rs to handle the subscribe field appropriately. [1] [2]

These changes ensure that the subscription status is consistently managed across different parts of the system, improving the reliability and maintainability of the code.

[sanity]

This will be very useful, it means a single API command to initiate syncing of contracts with the network bi-directionally.

[sanity]

@netsirius I merged this branch into my working River branch as it should simplify the state synchronization - I should probably have checked with you first to see if it's functional enough for me to use experimentally?