feat: add compose_hash_registered to provision response schema

Support skipping wallet interaction when compose hash is already
registered on-chain. The backend now returns this field during
provision, and the frontend can skip the addComposeHash transaction.

Author: Leechael

js/src/actions/cvms/provision_cvm_compose_file_update.test.ts

@@ -35,6 +35,7 @@ describe("provisionCvmComposeFileUpdate", () => {
     app_id: "app-123",
     device_id: "device-456",
     compose_hash: "abc123def456",
+    compose_hash_registered: false,
     kms_info: {
       id: "kms-123",
       slug: "test-kms",

js/src/actions/cvms/provision_cvm_compose_file_update.ts

@@ -126,6 +126,7 @@ export const ProvisionCvmComposeFileUpdateResultSchema = z
     device_id: z.string().nullable(),
     compose_hash: z.string(),
     kms_info: KmsInfoSchema.nullable().optional(),
+    compose_hash_registered: z.boolean().optional().default(false),
   })
   .passthrough();