fix(config): use valid UUID placeholders in example config and fix keyset error variant

Update cipherstash-proxy-example.toml to use valid placeholder UUIDs for
client_id and default_keyset_id now that EncryptConfig deserializes these
as Uuid types. Rename stale InvalidDatasetId error variant to
InvalidDefaultKeysetId with an accurate error message.

Author: tobyhede

cipherstash-proxy-example.toml

@@ -24,6 +24,6 @@ workspace_crn = "workspace_crn"
 client_access_key = "client_access_key"
 
 [encrypt]
-default_keyset_id = "default_keyset_id"
-client_id = "client_id"
+default_keyset_id = "00000000-0000-0000-0000-000000000000"
+client_id = "00000000-0000-0000-0000-000000000000"
 client_key = "client_key"

packages/cipherstash-proxy/src/config/tandem.rs

@@ -205,7 +205,7 @@ impl TandemConfig {
                                 value: "invalid UUID".to_string(),
                             }
                         } else {
-                            ConfigError::InvalidDatasetId
+                            ConfigError::InvalidDefaultKeysetId
                         }
                     }
                     s if s.contains("missing field") => {

packages/cipherstash-proxy/src/error.rs

@@ -125,8 +125,8 @@ pub enum ConfigError {
     #[error("Client key is not valid.")]
     InvalidClientKey,
 
-    #[error("Dataset id is not a valid UUID.")]
-    InvalidDatasetId,
+    #[error("default_keyset_id is not a valid UUID.")]
+    InvalidDefaultKeysetId,
 
     #[error("Server host {name} is not a valid server name")]
     InvalidServerName { name: String },