connect/disconnect reducers called when executing reducer from from CLI

[jdetter]

Description of Changes

• When you invoke a reducer from the CLI, now OnConnect and OnDisconnect are invoked in the module.

API and ABI

• This is a breaking change to the module ABI
• This is a breaking change to the module API
• This is a breaking change to the ClientAPI
• This is a breaking change to the SDK API
• This is a change in behavior that may be API breaking

If the API is breaking, please state below what will break

[gefjon]

This if/else chain is kinda grody, and I don't think it's necessary. Can this be:

if let Err(e) = module.call_identity_connected_disconnected(caller_identity, true).await {
    // handle error
}
let result = match module.call_reducer(whatever).await {
    // whatever
};

It also seems like the if let Err(e) = foo { return Err(whatever); } could be made into a helper function, something like:

fn with_status_code(code: StatusCode, err: impl std::string::ToString) -> impl Axum::IntoResponse {
    (code, err.to_string())
}

// handling an error
let result = module.call_reducer(caller_identity, None, &reducer, args)
    .map_err(|e| with_status_code(StatusCode::NOT_FOUND, e)?;

[gefjon]

Should we call disconnected somewhere in this block?