fix(clippy): resolve two lints that fail -Dwarnings on clippy 1.97

[kkdao]

Description

cargo clippy --all-targets --all-features -- -Dwarnings currently fails on master with two lints. Both are style-only; neither changes behaviour.

clippy::useless_conversion — oracles/src/tweaks/blindbit.rs:184

futures::stream::iter takes an IntoIterator, so calling .into_iter() on the map first is redundant.

clippy::question_mark — cli/v2/src/main.rs:413

The spawned task matched on the node error only to return it unchanged. Note that clippy's own suggestion (node.run().await?; followed by Ok(())) does not compile — with the explicit return Err(e) gone there is nothing left to infer the Result's error type from, so it fails with E0282. Returning the future's result directly is equivalent, avoids the annotation, and matches how blindbit_subscriber and the other tasks are spawned a few lines below.

These only fire on newer clippy — observed on 1.97 — which is likely why CI hasn't caught them yet.

Notes to the reviewers

Neither hunk can change runtime behaviour: stream::iter calls .into_iter() itself, and in the CLI the Result goes into a JoinHandle that nothing awaits, before or after.

Checklists

All Submissions:

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