rebrand: kusama → dicle

- Replace all kusama/Kusama references with dicle/Dicle
- Rename weight files from ksm_size to dcl_size
- Update papi-tests files from ksm to dcl
- Remove chain-specs/kusama.json files
- cargo check --workspace successful (Finished output)
- Update MAINNET_ROADMAP.md: FAZ 8 completed

pezkuwi/node/core/approval-voting/benches/approval-voting-regression-bench.rs

@@ -16,7 +16,7 @@
 
 //! approval-voting throughput test
 //!
-//! Approval Voting benchmark based on Kusama parameters and scale.
+//! Approval Voting benchmark based on Dicle parameters and scale.
 //!
 //! Subsystems involved:
 //! - approval-distribution

pezkuwi/node/core/candidate-validation/src/lib.rs

@@ -530,7 +530,7 @@ where
 		.iter()
 		.any(|v| keystore.has_keys(&[(v.to_raw_vec(), AuthorityDiscoveryId::ID)]));
 
-	// We could've checked discovery_keys but on Kusama validators.len() < discovery_keys.len().
+	// We could've checked discovery_keys but on Dicle validators.len() < discovery_keys.len().
 	let is_present_validator = session_info
 		.validators
 		.iter()

pezkuwi/node/core/dispute-coordinator/benches/dispute-coordinator-regression-bench.rs

@@ -16,7 +16,7 @@
 
 //! dispute-coordinator throughput test
 //!
-//! Dispute Coordinator benchmark based on Kusama parameters and scale.
+//! Dispute Coordinator benchmark based on Dicle parameters and scale.
 //!
 //! Subsystems involved:
 //! - dispute-coordinator

pezkuwi/node/core/dispute-coordinator/src/db/v1.rs

@@ -54,7 +54,7 @@ const CLEANED_VOTES_WATERMARK_KEY: &[u8; 23] = b"cleaned-votes-watermark";
 ///
 /// 300 is with session duration of 1 hour and 30 teyrchains around <3_000_000 key purges in the
 /// worst case. Which is already quite a lot, at the same time we have around 21_000 sessions on
-/// Kusama. This means at 300 purged sessions per session, cleaning everything up will take
+/// Dicle. This means at 300 purged sessions per session, cleaning everything up will take
 /// around 3 days. Depending on how severe disk usage becomes, we might want to bump the batch
 /// size, at the cost of risking issues at session boundaries (performance).
 #[cfg(test)]

pezkuwi/node/core/dispute-coordinator/src/tests.rs

@@ -186,7 +186,7 @@ impl Default for TestState {
 	fn default() -> TestState {
 		let p1 = Pair::from_string("//Polka", None).unwrap();
 		let p2 = Pair::from_string("//Hez", None).unwrap();
-		let p3 = Pair::from_string("//Kusama", None).unwrap();
+		let p3 = Pair::from_string("//Dicle", None).unwrap();
 		let validators = vec![
 			(Sr25519Keyring::Alice.pair(), Sr25519Keyring::Alice.to_seed()),
 			(Sr25519Keyring::Bob.pair(), Sr25519Keyring::Bob.to_seed()),
@@ -198,7 +198,7 @@ impl Default for TestState {
 			// Two more keys needed so disputes are not confirmed already with only 3 statements.
 			(p1, "//Polka".into()),
 			(p2, "//Hez".into()),
-			(p3, "//Kusama".into()),
+			(p3, "//Dicle".into()),
 		];
 
 		let validator_public = validators

pezkuwi/node/core/provisioner/src/metrics.rs

@@ -30,7 +30,7 @@ struct MetricsInner {
 
 	/// The following metrics track how many disputes/votes the runtime will have to process. These
 	/// will count all recent statements meaning every dispute from last sessions: 10 min on
-	/// Pezkuwichain, 60 min on Kusama and 4 hours on Pezkuwi. The metrics are updated only when
+	/// Pezkuwichain, 60 min on Dicle and 4 hours on Pezkuwi. The metrics are updated only when
 	/// the node authors a block, so values vary across nodes.
 	inherent_data_dispute_statement_sets: prometheus::Counter<prometheus::U64>,
 	inherent_data_dispute_statements: prometheus::CounterVec<prometheus::U64>,