Smash the singular Ciphersuite trait into multiple

This helps identify where the various functionalities are used, or rather, not
used. The `Ciphersuite` trait present in `patches/ciphersuite`, facilitating
the entire FCMP++ tree, only requires the markers _and_ canonical point
decoding. I've opened a PR to upstream such a trait into `group`
(https://github.com/zkcrypto/group/pull/68).

`WrappedGroup` is still justified for as long as `Group::generator` exists.
Moving `::generator()` to its own trait, on an independent structure (upstream)
would be massively appreciated. @tarcieri also wanted to update from
`fn generator()` to `const GENERATOR`, which would encourage further discussion
on https://github.com/zkcrypto/group/issues/32 and
https://github.com/zkcrypto/group/issues/45, which have been stagnant.

The `Id` trait is occasionally used yet really should be first off the chopping
block.

Finally, `WithPreferredHash` is only actually used around a third of the time,
which more than justifies it being a separate trait.

---

Updates `dalek_ff_group::Scalar` to directly re-export
`curve25519_dalek::Scalar`, as without issue. `dalek_ff_group::RistrettoPoint`
also could be replaced with an export of `curve25519_dalek::RistrettoPoint`,
yet the coordinator relies on how we implemented `Hash` on it for the hell of
it so it isn't worth it at this time. `dalek_ff_group::EdwardsPoint` can't be
replaced for an re-export of `curve25519_dalek::SubgroupPoint` as it doesn't
implement `zeroize`, `subtle` traits within a released, non-yanked version.
Relevance to https://github.com/serai-dex/serai/issues/201 and
https://github.com/dalek-cryptography/curve25519-dalek/issues/811#issuecomment-3247732746.

Also updates the `Ristretto` ciphersuite to prefer `Blake2b-512` over
`SHA2-512`. In order to maintain compliance with FROST's IETF standard,
`modular-frost` defines its own ciphersuite for Ristretto which still uses
`SHA2-512`.

message-queue/src/client.rs

@@ -4,10 +4,7 @@ use zeroize::{Zeroize, Zeroizing};
 use rand_core::OsRng;
 
 use dalek_ff_group::Ristretto;
-use ciphersuite::{
-  group::ff::{Field, PrimeField},
-  Ciphersuite,
-};
+use ciphersuite::{group::ff::PrimeField, WrappedGroup};
 use schnorr_signatures::SchnorrSignature;
 
 use tokio::{
@@ -22,8 +19,8 @@ use crate::{Service, Metadata, QueuedMessage, MessageQueueRequest, message_chall
 
 pub struct MessageQueue {
   pub service: Service,
-  priv_key: Zeroizing<<Ristretto as Ciphersuite>::F>,
-  pub_key: <Ristretto as Ciphersuite>::G,
+  priv_key: Zeroizing<<Ristretto as WrappedGroup>::F>,
+  pub_key: <Ristretto as WrappedGroup>::G,
   url: String,
 }
 
@@ -31,7 +28,7 @@ impl MessageQueue {
   pub fn new(
     service: Service,
     mut url: String,
-    priv_key: Zeroizing<<Ristretto as Ciphersuite>::F>,
+    priv_key: Zeroizing<<Ristretto as WrappedGroup>::F>,
   ) -> MessageQueue {
     // Allow MESSAGE_QUEUE_RPC to either be a full URL or just a hostname
     // While we could stitch together multiple variables, our control over this service makes this
@@ -46,16 +43,16 @@ impl MessageQueue {
   pub fn from_env(service: Service) -> MessageQueue {
     let url = env::var("MESSAGE_QUEUE_RPC").expect("message-queue RPC wasn't specified");
 
-    let priv_key: Zeroizing<<Ristretto as Ciphersuite>::F> = {
+    let priv_key: Zeroizing<<Ristretto as WrappedGroup>::F> = {
       let key_str =
         Zeroizing::new(env::var("MESSAGE_QUEUE_KEY").expect("message-queue key wasn't specified"));
       let key_bytes = Zeroizing::new(
         hex::decode(&key_str).expect("invalid message-queue key specified (wasn't hex)"),
       );
-      let mut bytes = <<Ristretto as Ciphersuite>::F as PrimeField>::Repr::default();
+      let mut bytes = <<Ristretto as WrappedGroup>::F as PrimeField>::Repr::default();
       bytes.copy_from_slice(&key_bytes);
       let key = Zeroizing::new(
-        Option::from(<<Ristretto as Ciphersuite>::F as PrimeField>::from_repr(bytes))
+        Option::from(<<Ristretto as WrappedGroup>::F as PrimeField>::from_repr(bytes))
           .expect("invalid message-queue key specified"),
       );
       bytes.zeroize();
@@ -79,7 +76,7 @@ impl MessageQueue {
   }
 
   pub async fn queue(&self, metadata: Metadata, msg: Vec<u8>) -> Result<(), String> {
-    let nonce = Zeroizing::new(<Ristretto as Ciphersuite>::F::random(&mut OsRng));
+    let nonce = Zeroizing::new(<Ristretto as WrappedGroup>::F::random(&mut OsRng));
     let nonce_pub = Ristretto::generator() * nonce.deref();
     let sig = SchnorrSignature::<Ristretto>::sign(
       &self.priv_key,
@@ -215,7 +212,7 @@ impl MessageQueue {
 
   pub async fn ack(&self, from: Service, id: u64) {
     // TODO: Should this use OsRng? Deterministic or deterministic + random may be better.
-    let nonce = Zeroizing::new(<Ristretto as Ciphersuite>::F::random(&mut OsRng));
+    let nonce = Zeroizing::new(<Ristretto as WrappedGroup>::F::random(&mut OsRng));
     let nonce_pub = Ristretto::generator() * nonce.deref();
     let sig = SchnorrSignature::<Ristretto>::sign(
       &self.priv_key,