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.

bridges/docs/high-level-overview.md

@@ -6,7 +6,7 @@ Kusama Bridge](./pezkuwi-kusama-bridge-overview.md).
 
 ## Purpose
 
-This repo contains all components required to build a trustless connection between standalone Substrate chains, that are
+This repo contains all components required to build a trustless connection between standalone Bizinikiwi chains, that are
 using GRANDPA finality, their teyrchains or any combination of those. On top of this connection, we offer a messaging
 pallet that provides means to organize messages exchange.
 
@@ -181,4 +181,4 @@ may perform its job. If on-demand relay is a teyrchain finality relay, it also r
 which is used to relay required relay chain headers.
 
 More: [Complex Relay Sequence Diagram](./complex-relay.html),
-[code](../relays/bin-substrate/src/cli/relay_headers_and_messages/).
+[code](../relays/bin-bizinikiwi/src/cli/relay_headers_and_messages/).

bridges/docs/pezkuwi-kusama-bridge-overview.md

@@ -61,7 +61,7 @@ is the relayer, which is following our rules:
   pays the full cost of the transaction;
 
 - we compensate the cost of message delivery and all required finality calls, if they are part of the same
-  [`frame_utility::batch_all`](https://github.com/paritytech/substrate/blob/891d6a5c870ab88521183facafc811a203bb6541/frame/utility/src/lib.rs#L326)
+  [`frame_utility::batch_all`](https://github.com/paritytech/bizinikiwi/blob/891d6a5c870ab88521183facafc811a203bb6541/frame/utility/src/lib.rs#L326)
   transaction. Of course, the calls inside the batch must be linked - e.g. the submitted teyrchain head must be used to
   prove messages. Relay header must be used to prove teyrchain head finality. If one of calls fails, or if they are not
   linked together, the relayer pays the full transaction cost.
@@ -126,6 +126,6 @@ bridge transactions with obsolete data from including into the block. We are rej
 - transactions, that are confirming delivery of already confirmed messages. If at least one of confirmations is new, the
   transaction is not rejected;
 
-- [`frame_utility::batch_all`](https://github.com/paritytech/substrate/blob/891d6a5c870ab88521183facafc811a203bb6541/frame/utility/src/lib.rs#L326)
+- [`frame_utility::batch_all`](https://github.com/paritytech/bizinikiwi/blob/891d6a5c870ab88521183facafc811a203bb6541/frame/utility/src/lib.rs#L326)
   transactions, that have both finality and message delivery calls. All restrictions from the [Compensating the Cost of
   Message Delivery Transactions](#compensating-the-cost-of-message-delivery-transactions) are applied.

bridges/docs/running-relayer.md

@@ -68,7 +68,7 @@ by lurking in the code.
 We also have the WiP prototype of relayers coordination protocol, where relayers will get some guarantee
 that their transactions will be prioritized over other relayers transactions at their assigned slots.
 That is planned for the future version of bridge and the progress is
-[tracked here](https://github.com/paritytech/parity-bridges-common/issues/2486).
+[tracked here](https://github.com/pezkuwichain/kurdistan-sdk/issues/85).
 
 </details>
 
@@ -256,7 +256,7 @@ image reference and source files, required to build relayer manually.
 
 Once you have the docker image, update variables and run the following script:
 ```sh
-export DOCKER_IMAGE=<image-of-substrate-relay>
+export DOCKER_IMAGE=<image-of-bizinikiwi-relay>
 
 export PEZKUWICHAIN_HOST=<pezkuwichain-ws-rpc-host-here>
 export PEZKUWICHAIN_PORT=<pezkuwichain-ws-rpc-port-here>
@@ -326,7 +326,7 @@ docker run \
     ..
     $DOCKER_IMAGE \
     relay-headers-and-messages bridge-hub-pezkuwichain-bridge-hub-zagros \
-    --prometheus-host 0.0.0.0 \ # tell `substrate-relay` binary to accept Prometheus endpoint
+    --prometheus-host 0.0.0.0 \ # tell `bizinikiwi-relay` binary to accept Prometheus endpoint
                                 # connections from everywhere
     ..
 ```