fix: Complete snowbridge pezpallet rebrand and critical bug fixes

- snowbridge-pezpallet-* → pezsnowbridge-pezpallet-* (201 refs)
- pallet/ directories → pezpallet/ (4 locations)
- Fixed pezpallet.rs self-include recursion bug
- Fixed sc-chain-spec hardcoded crate name in derive macro
- Reverted .pezpallet_by_name() to .pallet_by_name() (subxt API)
- Added BizinikiwiConfig type alias for zombienet tests
- Deleted obsolete session state files

Verified: pezsnowbridge-pezpallet-*, pezpallet-staking,
pezpallet-staking-async, pezframe-benchmarking-cli all pass cargo check

pezbridges/modules/relayers/README.md

@@ -0,0 +1,14 @@
+# Bridge Relayers Pezpallet
+
+The pezpallet serves as a storage for pending bridge relayer rewards. Any runtime component may register reward
+to some relayer for doing some useful job at some messages lane. Later, the relayer may claim its rewards
+using the `claim_rewards` call.
+
+The reward payment procedure is abstracted from the pezpallet code. One of possible implementations, is the
+[`PayLaneRewardFromAccount`](../../primitives/relayers/src/lib.rs), which just does a `Currency::transfer`
+call to relayer account from the relayer-rewards account, determined by the message lane id.
+
+We have two examples of how this pezpallet is used in production. Rewards are registered at the target chain to
+compensate fees of message delivery transactions (and linked finality delivery calls). At the source chain, rewards
+are registered during delivery confirmation transactions. You may find more information about that in the
+[Kusama <> PezkuwiChain bridge](../../docs/pezkuwi-kusama-bridge-overview.md) documentation.