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_offchain_workers.rs

@@ -1,8 +1,8 @@
 //! # Offchain Workers
 //!
-//! This reference document explains how offchain workers work in Substrate and FRAME. The main
+//! This reference document explains how offchain workers work in Bizinikiwi and FRAME. The main
 //! focus is upon FRAME's implementation of this functionality. Nonetheless, offchain workers are a
-//! Substrate-provided feature and can be used with possible alternatives to [`frame`] as well.
+//! Bizinikiwi-provided feature and can be used with possible alternatives to [`frame`] as well.
 //!
 //! Offchain workers are a commonly misunderstood topic, therefore we explain them bottom-up,
 //! starting at the fundamentals and then describing the developer interface.
@@ -11,11 +11,11 @@
 //!
 //! Recall from [`crate::reference_docs::wasm_meta_protocol`] that the node and the runtime
 //! communicate with one another via host functions and runtime APIs. Many of these interactions
-//! contribute to the actual state transition of the blockchain. For example [`sp_api::Core`] is the
+//! contribute to the actual state transition of the blockchain. For example [`pezsp_api::Core`] is the
 //! main runtime API that is called to execute new blocks.
 //!
 //! Offchain workers are in principle not different in any way: It is a runtime API exposed by the
-//! wasm blob ([`sp_offchain::OffchainWorkerApi`]), and the node software calls into it when it
+//! wasm blob ([`pezsp_offchain::OffchainWorkerApi`]), and the node software calls into it when it
 //! deems fit. But, crucially, this API call is different in that:
 //!
 //! 1. It can have no impact on the state ie. it is _OFF (the) CHAIN_. If any state is altered
@@ -25,7 +25,7 @@
 //!
 //! > The main way through which an offchain worker can interact with the state is by submitting an
 //! > extrinsic to the chain. This is the ONLY way to alter the state from an offchain worker.
-//! > [`pallet_example_offchain_worker`] provides an example of this.
+//! > [`pezpallet_example_offchain_worker`] provides an example of this.
 //!
 //!
 //! Given the "Off Chain" nature of this API, it is important to remember that calling this API is
@@ -33,16 +33,16 @@
 //! the execution of your blockchain because no state is altered no matter the execution of the
 //! offchain worker API.
 //!
-//! Substrate's CLI allows some degree of configuration about this, allowing node operators to
+//! Bizinikiwi's CLI allows some degree of configuration about this, allowing node operators to
 //! specify when they want to run the offchain worker API. See
-//! [`sc_cli::RunCmd::offchain_worker_params`].
+//! [`pezsc_cli::RunCmd::offchain_worker_params`].
 //!
 //! ## Nondeterministic Execution
 //!
 //! Needless to say, given the above description, the code in your offchain worker API can be
 //! nondeterministic, as it is not part of the blockchain's STF, so it can be executed at unknown
 //! times, by unknown nodes, and has no impact on the state. This is why an HTTP
-//! ([`sp_runtime::offchain::http`]) API is readily provided to the offchain worker APIs. Because
+//! ([`pezsp_runtime::offchain::http`]) API is readily provided to the offchain worker APIs. Because
 //! there is no need for determinism in this context.
 //!
 //! > A common mistake here is for novice developers to see this HTTP API, and imagine that
@@ -55,7 +55,7 @@
 //!
 //! [`frame`] provides a simple API through which pallets can define offchain worker functions. This
 //! is part of [`frame::traits::Hooks`], which is implemented as a part of
-//! [`frame::pallet_macros::hooks`].
+//! [`frame::pezpallet_macros::hooks`].
 //!
 //! ```
 //! #[frame::pallet]
@@ -63,7 +63,7 @@
 //! 	use frame::prelude::*;
 //!
 //! 	#[pallet::config]
-//! 	pub trait Config: frame_system::Config {}
+//! 	pub trait Config: pezframe_system::Config {}
 //!
 //! 	#[pallet::pallet]
 //! 	pub struct Pallet<T>(_);
@@ -77,27 +77,27 @@
 //! }
 //! ```
 //!
-//! Additionally, [`sp_runtime::offchain`] provides a set of utilities that can be used to moderate
+//! Additionally, [`pezsp_runtime::offchain`] provides a set of utilities that can be used to moderate
 //! the execution of offchain workers.
 //!
-//! ## Think Twice: Why Use Substrate's Offchain Workers?
+//! ## Think Twice: Why Use Bizinikiwi's Offchain Workers?
 //!
 //! Consider the fact that in principle, an offchain worker code written using the above API is no
 //! different than an equivalent written with an _actual offchain interaction library_, such as
-//! [Pezkuwi-JS](https://polkadot.js.org/docs/), or any of the other ones listed [here](https://github.com/substrate-developer-hub/awesome-substrate?tab=readme-ov-file#client-libraries).
+//! [Pezkuwi-JS](https://polkadot.js.org/docs/), or any of the other ones listed [here](https://github.com/bizinikiwi-developer-hub/awesome-bizinikiwi?tab=readme-ov-file#client-libraries).
 //!
 //! They can both read from the state, and have no means of updating the state, other than the route
 //! of submitting an extrinsic to the chain. Therefore, it is worth thinking twice before embedding
-//! a logic as a part of Substrate's offchain worker API. Does it have to be there? Can it not be a
+//! a logic as a part of Bizinikiwi's offchain worker API. Does it have to be there? Can it not be a
 //! simple, actual offchain application that lives outside of the chain's WASM blob?
 //!
 //! Some of the reasons why you might want to do the opposite, and actually embed an offchain worker
 //! API into the WASM blob are:
 //!
 //! * Accessing the state is easier within the `offchain_worker` function, as it is already a part
-//!   of the runtime, and [`frame::pallet_macros::storage`] provides all the tools needed to read
+//!   of the runtime, and [`frame::pezpallet_macros::storage`] provides all the tools needed to read
 //!   the state. Other client libraries might provide varying degrees of capability here.
-//! * It will be updated in synchrony with the runtime. A Substrate's offchain application is part
+//! * It will be updated in synchrony with the runtime. A Bizinikiwi's offchain application is part
 //!   of the same WASM blob, and is therefore guaranteed to be up to date.
 //!
 //! For example, imagine you have modified a storage item to have a new type. This will possibly
@@ -111,4 +111,4 @@
 //!
 //! - <https://forum.polkadot.network/t/offchain-workers-design-assumptions-vulnerabilities/2548>
 //! - <https://exchange.pezkuwichain.app/questions/11058/how-can-i-create-ocw-that-wont-activates-every-block-but-will-activates-only-w/11060#11060>
-//! - [Offchain worker example](https://github.com/pezkuwichain/pezkuwi-sdk/tree/master/substrate/frame/examples/offchain-worker)
+//! - [Offchain worker example](https://github.com/pezkuwichain/pezkuwi-sdk/tree/master/bizinikiwi/pezframe/examples/offchain-worker)