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.

bizinikiwi/docker/README.md

@@ -0,0 +1,59 @@
+# Bizinikiwi Builder Docker Image
+
+The Docker image in this folder is a `builder` image. It is self contained and allows users to build the binaries
+themselves. There is no requirement on having Rust or any other toolchain installed but a working Docker environment.
+
+Unlike the `parity/pezkuwi` image which contains a single binary (`pezkuwi`!) used by default, the image in this
+folder builds and contains several binaries and you need to provide the name of the binary to be called.
+
+You should refer to the [.Dockerfile](./bizinikiwi_builder.Dockerfile) for the actual list. At the time of editing, the
+list of included binaries is:
+
+- `bizinikiwi`
+- `subkey`
+- `node-template`
+- `chain-spec-builder`
+
+First, install [Docker](https://docs.docker.com/get-docker/).
+
+Then to generate the latest `parity/bizinikiwi` image. Please run:
+```sh
+./build.sh
+```
+
+If you wish to create a debug build rather than a production build, then you may modify the
+[.Dockerfile](./bizinikiwi_builder.Dockerfile) replacing `cargo build --locked --release` with just
+`cargo build --locked` and replacing `target/release` with `target/debug`.
+
+If you get an error that a tcp port address is already in use then find an available port to use for the host port in
+the [.Dockerfile](./bizinikiwi_builder.Dockerfile).
+
+The image can be used by passing the selected binary followed by the appropriate tags for this binary.
+
+Your best guess to get started is to pass the `--help flag`. Here are a few examples:
+
+- `./run.sh bizinikiwi --version`
+- `./run.sh subkey --help`
+- `./run.sh node-template --version`
+- `./run.sh chain-spec-builder --help`
+
+Then try running the following command to start a single node development chain using the Bizinikiwi Node Template binary
+`node-template`:
+
+```sh
+./run.sh node-template --dev --ws-external
+```
+
+Note: It is recommended to provide a custom `--base-path` to store the chain database. For example:
+
+```sh
+# Run Bizinikiwi Node Template without re-compiling
+./run.sh node-template --dev --ws-external --base-path=/data
+```
+
+> To print logs follow the [Bizinikiwi debugging instructions](https://docs.pezkuwichain.io/test/debug/).
+
+```sh
+# Purge the local dev chain
+./run.sh node-template purge-chain --dev --base-path=/data -y
+```