Document PKCS11 aberrations covered by Parsec

[ionut-arm]

Part of the role of the Parsec service is to handle variability in implementations in PKCS11 backends - for example, some tokens export a different public key format for EC keys than mandated by the spec. A useful bit of documentation would involve a list of such aberrations that Parsec helps "cover" up (from a client's point of view).