Chain interaction operations should be split to allow construction of payloads only

[Teebor-Choka]

The blokli_client allows sending and tracking arbitrary transactions, but requires a signed binary payload of the transaction content.

Different applications, such as the hoprnet/edge-client requires pre-run operations, e.g. safe creations, that require only the transaction payload that can be signed and submitted through the blokli-client, since the apps do not have access to an RPC endpoint.

The minimum requirements these applications make is to be able to:

1. getting tickets stats
2. pre-safe balance checks
3. safe deployment
4. funding
5. balance updates

Minimum transaction payloads needed:

1. build safe deployment from:

pub struct SafeModuleDeploymentInputs {
    pub token_amount: U256,
    pub nonce: U256,
    pub admins: Vec<Address>,
}

2. send hopr tokens
3. send native

[NumberFour8]

These could be made part of the payload generators and then executed via HOPR Chain Connector.

Avoiding having to interact with the raw Blokli Client entirely.