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

pezcumulus/teyrchains/runtimes/bridge-hubs/bridge-hub-zagros/src/bridge_common_config.rs

@@ -16,10 +16,10 @@
 
 //! Bridge definitions that can be used by multiple BridgeHub flavors.
 //! All configurations here should be dedicated to a single chain; in other words, we don't need two
-//! chains for a single pallet configuration.
+//! chains for a single pezpallet configuration.
 //!
-//! For example, the messaging pallet needs to know the sending and receiving chains, but the
-//! GRANDPA tracking pallet only needs to be aware of one chain.
+//! For example, the messaging pezpallet needs to know the sending and receiving chains, but the
+//! GRANDPA tracking pezpallet only needs to be aware of one chain.
 
 use super::{weights, AccountId, Balance, Balances, BlockNumber, Runtime, RuntimeEvent};
 use crate::{
@@ -43,7 +43,7 @@ parameter_types! {
 	pub const RelayerStakeReserveId: [u8; 8] = *b"brdgrlrs";
 }
 
-/// Showcasing that we can handle multiple different rewards with the same pallet.
+/// Showcasing that we can handle multiple different rewards with the same pezpallet.
 #[derive(
 	Clone,
 	Copy,