FAZ 1 Complete: Workspace compile fixes, warning cleanup, version bumps

- Fixed is_using_frame_crate() macro to check for pezframe/pezkuwi_sdk
- Removed disable_pezframe_system_supertrait_check temporary bypasses
- Feature-gated storage-benchmark and teyrchain-benchmarks code
- Fixed dead_code warnings with underscore prefix (_Header)
- Removed unused imports and shadowing use statements
- Version bumps: procedural-tools 10.0.1, benchmarking-cli 32.0.1,
  docs 0.0.2, minimal-runtime 0.0.1, yet-another-teyrchain 0.6.1, umbrella 0.1.2
- Updated MAINNET_ROADMAP.md with FAZ 1 completion status

docs/sdk/src/meta_contributing.rs

@@ -82,9 +82,9 @@
 //!
 //!
 //! ```
-//! #[frame::pezpallet(dev_mode)]
+//! #[pezframe::pezpallet(dev_mode)]
 //! pub mod pezpallet {
-//! #   use frame::prelude::*;
+//! #   use pezframe::prelude::*;
 //! #   #[pezpallet::config]
 //! #   pub trait Config: pezframe_system::Config {}
 //! #   #[pezpallet::pezpallet]
@@ -105,9 +105,9 @@
 //! explained in [`crate::reference_docs::frame_runtime_types`]. Build on top of this!
 //! * Then, what is `origin`? Just an account id? [`crate::reference_docs::frame_origin`].
 //! * Then, what is `DispatchResult`? Why is this called *dispatch*? Probably something that can be
-//! explained in the documentation of [`frame::prelude::DispatchResult`].
+//! explained in the documentation of [`pezframe::prelude::DispatchResult`].
 //! * Why is `"SomeStaticString"` a valid error? Because there is implementation for it that you can
-//!   see [here](frame::prelude::DispatchError#impl-From<%26'static+str>-for-DispatchError).
+//!   see [here](pezframe::prelude::DispatchError#impl-From<%26'static+str>-for-DispatchError).
 //!
 //!
 //! All of these are examples of underlying information that a contributor should: