Revoke the customer-registered public key

After revocation, new incidents fall back to server-side encryption (Tuteliq holds the key). Existing incidents stay encrypted under the previous key and remain readable only with its private key. Common reason to revoke: key compromise (then immediately register a new one).