Improve the process of getting a handle to a specific wallet with Kmd

[manuelmauro]

This is a snippet of the current workflow.

    let list_response = kmd.list_wallets()?;
    let wallet_id = match list_response
        .wallets
        .into_iter()
        .find(|wallet| wallet.name == "unencrypted-default-wallet")
    {
        Some(wallet) => wallet.id,
        None => return Err("Wallet not found".into()),
    };
    let init_response = kmd.init_wallet_handle(&wallet_id, "")?;
    let wallet_handle_token = init_response.wallet_handle_token;
    println!("Wallet Handle: {}", wallet_handle_token);

[manuelmauro]

@i-schuetz do you have any idea about this? I am thinking that the crate algonaut_client might stay very low-level with functions almost 1-to-1 with Algorand's API, while improving the ergonomics in the parent algonaut crate or in a new one. In this case adding a struct with a function like get(wallet_name: &str).

[ivnsch]

Yeah, this shouldn't be added to the client. I'd probably create a v1::Kmd that wraps around the client and adds convenience like this. You could rename the current Kmd in KmdBuilder or similar.

[manuelmauro]

Great, seems a good solution! I only have mixed feelings on builders' naming convention. I noticed that reqwest follows this convention while crates like actix seems not to.