feat: Rebrand Polkadot/Substrate references to PezkuwiChain

This commit systematically rebrands various references from Parity Technologies'
Polkadot/Substrate ecosystem to PezkuwiChain within the kurdistan-sdk.

Key changes include:
- Updated external repository URLs (zombienet-sdk, parity-db, parity-scale-codec, wasm-instrument) to point to pezkuwichain forks.
- Modified internal documentation and code comments to reflect PezkuwiChain naming and structure.
- Replaced direct references to  with  or specific paths within the  for XCM, Pezkuwi, and other modules.
- Cleaned up deprecated  issue and PR references in various  and  files, particularly in  and  modules.
- Adjusted image and logo URLs in documentation to point to PezkuwiChain assets.
- Removed or rephrased comments related to external Polkadot/Substrate PRs and issues.

This is a significant step towards fully customizing the SDK for the PezkuwiChain ecosystem.

docs/sdk/src/reference_docs/frame_logging.rs

@@ -18,7 +18,7 @@
 //! ```
 //!
 //! within the pallet, if you want to use the standard `println!`, it needs to be wrapped in
-//! [`sp_std::if_std`]. Of course, this means that this print code is only available to you in the
+//! [`pezsp_std::if_std`]. Of course, this means that this print code is only available to you in the
 //! `std` compiler flag, and never present in a wasm build.
 //!
 //! ```
@@ -27,7 +27,7 @@
 //! 	struct Pallet;
 //! 	impl Pallet {
 //! 		fn print() {
-//! 			sp_std::if_std! {
+//! 			pezsp_std::if_std! {
 //! 				println!("Hello, world!");
 //! 			}
 //! 		}
@@ -60,7 +60,7 @@
 //! More conveniently, the `frame` umbrella crate re-exports the log crate as [`frame::log`].
 //!
 //! Then, the pallet can use this crate to emit log statements. In this statement, we use the info
-//! level, and the target is `pallet-example`.
+//! level, and the target is `pezpallet-example`.
 //!
 //! ```
 //! mod pallet {
@@ -68,38 +68,38 @@
 //!
 //! 	impl Pallet {
 //! 		fn logs() {
-//! 			frame::log::info!(target: "pallet-example", "Hello, world!");
+//! 			frame::log::info!(target: "pezpallet-example", "Hello, world!");
 //! 		}
 //! 	}
 //! }
 //! ```
 //!
 //! This will in itself just emit the log messages, **but unless if captured by a logger, they will
-//! not go anywhere**. [`sp_api`] provides a handy function to enable the runtime logging:
+//! not go anywhere**. [`pezsp_api`] provides a handy function to enable the runtime logging:
 //!
 //! ```
 //! // in your test
 //! fn it_also_prints() {
-//! 	sp_api::init_runtime_logger();
+//! 	pezsp_api::init_runtime_logger();
 //! 	// call into your pallet, and now it will print `log` statements.
 //! }
 //! ```
 //!
-//! Alternatively, you can use [`sp_tracing::try_init_simple`].
+//! Alternatively, you can use [`pezsp_tracing::try_init_simple`].
 //!
 //! `info`, `error` and `warn` logs are printed by default, but if you want lower level logs to also
 //! be printed, you must to add the following compiler flag:
 //!
 //! ```text
-//! RUST_LOG=pallet-example=trace cargo test
+//! RUST_LOG=pezpallet-example=trace cargo test
 //! ```
 //!
 //! ## Enabling Logs in Production
 //!
-//! All logs from the runtime are emitted by default, but there is a feature flag in [`sp_api`],
+//! All logs from the runtime are emitted by default, but there is a feature flag in [`pezsp_api`],
 //! called `disable-logging`, that can be used to disable all logs in the runtime. This is useful
 //! for production chains to reduce the size and overhead of the wasm runtime.
-#![doc = docify::embed!("../../substrate/primitives/api/src/lib.rs", init_runtime_logger)]
+#![doc = docify::embed!("../../bizinikiwi/primitives/api/src/lib.rs", init_runtime_logger)]
 //!
 //! Similar to the above, the proper `RUST_LOG` must also be passed to your compiler flag when
 //! compiling the runtime.
@@ -115,7 +115,7 @@
 //!
 //! Under the hood, logging is another instance of host functions under the hood (as defined in
 //! [`crate::reference_docs::wasm_meta_protocol`]). The runtime uses a set of host functions under
-//! [`sp_io::logging`] and [`sp_io::misc`] to emit all logs and prints. You typically do not need to
+//! [`pezsp_io::logging`] and [`pezsp_io::misc`] to emit all logs and prints. You typically do not need to
 //! use these APIs directly.
 //!
 //! ## Using Logging in Production
@@ -124,12 +124,12 @@
 //! and can lead to consensus issues. This is because with the introduction of
 //! [`crate::guides::enable_pov_reclaim`], the node side code will track the storage changes, and
 //! tries to update the onchain record of the `proof_size` weight used (stored in
-//! [`frame_system::BlockWeight`]) after the block is executed.
+//! [`pezframe_system::BlockWeight`]) after the block is executed.
 //!
 //! If one node has a different log level enabled than the rest of the network, and the extra logs
 //! impose additional storage reads, then the amount of `proof_size` weight reclaimed into
-//! [`frame_system::BlockWeight`] will be different, causing a state root mismatch, which is
-//! typically a fatal error emitted from [`frame_executive`].
+//! [`pezframe_system::BlockWeight`] will be different, causing a state root mismatch, which is
+//! typically a fatal error emitted from [`pezframe_executive`].
 //!
 //! This also can also happen in a teyrchain context, and cause discrepancies between the relay
 //! chain and the teyrchain, when execution the Teyrchain Validation Function (PVF) on the relay