Problem Description:

Since validated and certified content will use different keys for signing collections, we want to make sure that user's don't accidentally use the wrong signature for the wrong collection

Proposed Solution:

On the approval dashboard check the public key fingerprint for the collection signature that is being uploaded and verify that it matches the key that was used to sign the last version of the collection that was uploaded. If there is a public key mismatch, raise an alert modal that requires the user to confirm that the signature is correct.