feat: encrypted JSON should use the new EQL schema

[freshtonic]

The new EQL schema payload corresponds to this Rust type:

#[derive(Debug, Deserialize, Serialize)]
pub struct EqlEncrypted {
        #[serde(rename = "c", with = "option_mp_base85")]
        ciphertext: Option<EncryptedRecord>,
        #[serde(rename = "i")]
        identifier: Identifier,
        #[serde(rename = "v")]
        version: u16,

        #[serde(rename = "o")]
        ore_index: Option<Vec<String>>,
        #[serde(rename = "m")]
        match_index: Option<Vec<u16>>,
        #[serde(rename = "u")]
        unique_index: Option<String>,

        #[serde(rename = "s")]
        selector: Option<String>,

        #[serde(rename = "b")]
        blake3_index: Option<String>,

        #[serde(rename = "ocf")]
        ore_cclw_fixed_index: Option<String>,
        #[serde(rename = "ocv")]
        ore_cclw_var_index: Option<String>,

        #[serde(rename = "sv")]
        ste_vec_index: Option<Vec<EqlEncrypted>>,
    }

Acknowledgment

By submitting this pull request, I confirm that CipherStash can use, modify, copy, and redistribute this contribution, under the terms of CipherStash's choice.

[tobyhede]

Do we add tests for the format?
Or cover with comprehensive integration tests?

[freshtonic]

Closing in favour of #222