Enable force debug in revive dev node (#10383)

This change ensures that all types that implement `RuntimeDebug` are
fully displayed in log output of the revive dev node, instead of just
showing `<wasm:stripped>`.

Unfortunately, the trait `RuntimeDebugNoBound`, that we also use
frequently in pallet-revive, is not affected and will still output
`<wasm:stripped>` (it does not check for the `force-debug` feature flag,
instead it only fully outputs values when either one of the features
`std` or `try_runtime` is enabled – this is something we implement as a
general change).

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: pgherveou <pgherveou@gmail.com>

Author: 3 people

Cargo.lock

@@ -0,0 +1,13 @@
+title: Enable force debug in revive dev node
+doc:
+- audience: Runtime Dev
+  description: "This change ensures that all types that implement `RuntimeDebug` are\
+    \ fully displayed in log output of the revive dev node, instead of just showing\
+    \ `<wasm:stripped>`.\n\nUnfortunately, the trait `RuntimeDebugNoBound`, that we\
+    \ also use frequently in pallet-revive, is not affected and will still output\
+    \ `<wasm:stripped>` (it does not check for the `force-debug` feature flag, instead\
+    \ it only fully outputs values when either one of the features `std` or `try_runtime`\
+    \ is enabled \u2013\_this is something we implement as a general change)."
+crates:
+- name: revive-dev-runtime
+  bump: patch

prdoc/pr_10383.prdoc

@@ -25,6 +25,7 @@ polkadot-sdk = { workspace = true, features = [
 ] }
 scale-info = { workspace = true }
 serde_json = { workspace = true, default-features = false, features = ["alloc"] }
+sp-debug-derive = { workspace = true, features = ["force-debug"] }
 
 [build-dependencies]
 polkadot-sdk = { optional = true, workspace = true, features = ["substrate-wasm-builder"] }
@@ -36,4 +37,5 @@ std = [
 	"polkadot-sdk/std",
 	"scale-info/std",
 	"serde_json/std",
+	"sp-debug-derive/std",
 ]