Ns/versionize zk

[nsarlin-zama]

closes: please link all relevant issues

PR content/description

Versionize the ProvenCompactCiphertextList.

Arkworks serialization

For this I changed a bit the way the serialization of arkworks data is handled.
Arkworks use a custom serialization framework (not serde). The reason they state for this is that they want to be able to compress the elliptic curve data during serialization.

However, their serialization scheme is "code oriented" (whereas serde is more "data oriented" because the code serialization is generated automatically based only on type definitions). It means that for backward compatibility we need to check not only the types but also the serialization functions, where subtle breaking changes can occur.

This PR changes this by defining serializable counterparts to arkworks types. These types then simply derive "serialize/deserialize" so they can be easily versioned.
The compression is still optionally supported. the "SerializableAffine" type is defined as an enum:

pub enum SerializableAffine<F> {
    Infinity,
    Compressed { x: F, take_largest_y: bool },
    Uncompressed { x: F, y: F },
}

The "compression" happens when this type is created from arkwork's Affine type. Using an enum is easier for versioning than the bitflags system used by arkworks, and is directly compatible with serde.

To handle compression, I added a trait Compressible. Now to serialize a compressed version we do:

bincode::serialize(&public_params.compress());

The dependency to ark_serialize has been removed.

pke/pke_v2

Both have been versioned in this PR, a commit has been added to use pke_v2. It can be removed if needed.

Verify

The Verify option of ark_serialize is currently not supported, which is a regression. I think it should be moved to the conformance API for uniformization.

Check-list:

• Adds a test the data repo for ProvenCompactCiphertextList
• Enable the zk in tfhe-lints
• Docs have been added / updated (for bug fixes / features)
• Chose between zk v1 or v2
• Relevant issues are marked as resolved/closed, related issues are linked in the description
• Check for breaking changes (including serialization changes) and add them to commit message following the conventional commit specification