electrsd: include in workspace and CI

[satsfy]

Closes #552

• Include electrsd in the workspace so it is built, linted, and tested alongside the other crates, mirroring the bitcoind crate pattern.
• Apply cargo fmt and clippy fixes in electrsd
• Updates the lockfiles with ./contrib/update-lock-files.sh
• Make electrs_0_10_6 the default version feature. Version features are now chained like bitcoind as a version cascade: electrs_0_10_6 -> 0_9_11 -> 0_9_1 -> 0_8_10 -> esplora. --all-features resolves to 0.10.6.
• Version-specific behavior is identified in versions.rs with legible constants USE_LEGACY_COOKIE (replacing old legacy feature), USE_JSONRPC_IMPORT, USE_VERBOSE_ARG.
• Esplora is tested with --no-default-features so it does not accidentally combine with the default electrs version.
• no-download job now enables bitcoind_download because it still needs a bitcoind binary while using the system-provided ELECTRS_EXEC.
• Corrected the bitcoind 23_2 feature name in ee9443c.
• Make electrsd CI coverage easier to debug by putting RUST_LOG=debug on electrsd jobs.

Tests now include electrsd. Check by running: cargo test --all-features

I've had various versions problems. Ran a CI matrix of every bitcoin version and electrds in Ubuntu 24.04 to understand what would work with what.

[satsfy]

One thing I thought to include is a default electrsd version, like bitcoind in 0_17_2, I suppose either 0_8_10 or 0_10_6. I have not included a default because it required including std (for bitreq's get() to download), and I'm not sure if it's this PR's scope.

Edit: I suppose we need the default so tests work with an explicit version.

[satsfy]

Latest force push improves the legibility of the solution, sets a default electrs version, reworked the version feature graph so the cfg cascade in versions.rs is unambiguous. Replaced the legacy feature with versions::USE_LEGACY_COOKIE so --all-features tests pass.

[tcharding]

Needs rebase mate. Out of interest what made you go with electrs_0_8_10 instead of electrs_0_10_6?

[satsfy]

Great point, I made a mistake regarding 0_8_10. I had matched bitcoind pattern, but accidentally reversed the order of the versions. The highest version in bitcoind chain is the lowest, meanwhile I put the highest for electrsd. Latest rebase reverses that order.

EDIT: The problem with v0.10.6 in CI was caused by using the legacy --jsonrpc-import arg after 0.8.10. That nuance was lost on me because execution would fail on my Ubuntu 22.04 for requiring GLIBC 2.38 to test 0.10.6 properly.

[satsfy]

On the latest rebase:

• New electrs feature version cascade: electrs_0_10_6 -> 0_9_11 -> 0_9_1 -> 0_8_10 -> esplora.
• Centralized the version-specific behavior in versions.rs with legible constants USE_LEGACY_COOKIE, USE_JSONRPC_IMPORT, USE_VERBOSE_ARG.
• Esplora is tested with --no-default-features so it does not accidentally combine with the default electrs version.
• no-download job now enables bitcoind_download because it still needs a bitcoind binary while using the system-provided ELECTRS_EXEC.
• Corrected the bitcoind 23_2 feature name in ee9443c (is this correct? Should I have done it in a separate PR)?
• Optional change that I think should be merged: make electrsd CI coverage easier to debug by putting RUST_LOG=debug on electrsd jobs.

[tcharding]

Can we separate the fmt changes from actual code changes in c61ea18

[tcharding]

These feature gates are making my eyes bleed. not, all, not - is there any way we can make this easier to reason about?

[satsfy]

I simplified version conditions with any like

#[cfg(any(feature = "electrs_0_9_1", not(feature = "electrs_0_8_10")))]

And also used simpler conditions like crate::versions::IS_ELECTRS_0_8_10 in another spot.

[satsfy]

Latest rebase:

• Split rustfmt cleanup (17866ee), lint error fixes (33158b2) and new rbmt lint configuration (9143712).
• Fix Cargo.toml link typo (28022c5)
• Simplifies version conditions:
  • Using any in #[cfg(any(feature = "electrs_0_9_1", not(feature = "electrs_0_8_10")))]
  • or crate::versions::IS_ELECTRS_0_8_10.

[satsfy]

Latest rebase updates lockfiles because of upstream changes to fix ci