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

docs/sdk/src/reference_docs/glossary.rs

@@ -66,14 +66,14 @@
 //! included into a block and leads to some action. This includes user-initiated transactions as
 //! well as inherents which are placed into the block by the block-builder.
 //!
-//! #### Pallet
+//! #### Pezpallet
 //!
 //! Similar to software modules in traditional programming, [FRAME](frame) pallets in Bizinikiwi are
 //! modular components that encapsulate distinct functionalities or business logic. Just as
 //! libraries or modules are used to build and extend the capabilities of a software application,
 //! pallets are the foundational building blocks for constructing a blockchain's runtime with frame.
 //! They enable the creation of customizable and upgradeable networks, offering a composable
-//! framework for a Bizinikiwi-based blockchain. Each pallet can be thought of as a plug-and-play
+//! framework for a Bizinikiwi-based blockchain. Each pezpallet can be thought of as a plug-and-play
 //! module, enhancing the blockchain's functionality in a cohesive and integrated manner.
 //!
 //! #### Full Node