Configure log level and DNS resolver

[rustaceanrob]

Description

Partial steps towards #700 that are uncontroversial feature additions. The LogLevel enum allows for filtering the Log::Debug messages, which are mostly used for debugging and require a string allocation. Without these messages the node should sync even faster in a production application that communicates with a UI. Other developers may have a preferred DNS resolver they would like to point their users at. That is easily configurable as well.

Notes to the reviewers

It appears the lockfile was not updated when the Cargo.toml changed versions.

Checklists

All Submissions:

• I've signed all my commits
• I followed the contribution guidelines
• I ran cargo fmt and cargo clippy before committing

New Features:

• I've added tests for the new feature
• I've added docs for the new feature

Bugfixes:

• This pull request breaks the existing API
• I've added tests to reproduce the issue which are now passing
• I'm linking the issue being fixed by this PR

[rustaceanrob]

Rebased

[thunderbiscuit]

Looks good to me, I'd merge this one next.

One thing I just tried locally (it's my first time using a straight remote type that doesn't need wrapping with the proc macros) is the procedure defined on this page: https://mozilla.github.io/uniffi-rs/latest/types/remote_ext_types.html. All live Kyoto tests pass on my end.

// Remove this line
// use bdk_kyoto::kyoto::LogLevel as BDKLogLevel;

// Replace with
type LogLevel = bdk_kyoto::kyoto::LogLevel;

/// Select the category of messages for the node to emit.
#[uniffi::remote(Enum)]
pub enum LogLevel {
    /// Send `Log::Debug` messages. These messages are intended for debugging or troubleshooting
    /// node operation.
    Debug,
    /// Omit `Log::Debug` messages, including their memory allocations. Ideal for a production
    /// application that uses minimal logging.
    Warning,
}

// The From<LogLevel> for BDKLogLevel trait implementation can be deleted

How do you feel about this approach? It basically removes the requirement to write a wrapper on the type. There are other places where we should use this, for example on the Network enum (and potentially on a bunch of errors? Will need to look into that).

[rustaceanrob]

I took a shallow attempt at this and overlooked uniffi::Remote. This is much better, thanks for the detailed instructions. Updated now

[thunderbiscuit]

ACK bb89233.

[thunderbiscuit]

@reez if you don't mind I'll merge this one once the tests finish and then you can rebase #711?

[reez]

@reez if you don't mind I'll merge this one once the tests finish and then you can rebase #711?

absolutely, no problem, thanks for the heads up