Revert "🤝 Account for signature in verification result cache."

This reverts commit 4b8dcb3f1486f3a35751d45ccf38d7d4c5dbbc70.

Reason for revert:

The downstream change could not easily land. I think this change is not only making compiling issue but has some logic change so the downstream tests will fail.

Original change's description:
> 🤝 Account for signature in verification result cache.
> 
> Previously we didn't cache the signature of the package with the
> verification result - this caused bugs when someone is developing and
> switching signatures around.
> 
> Additionally removed checking the cache from the main verification
> logic, this resulted in verification never failing for an app that it
> had previously succeeded with (originally this made sense when we had
> two separate stores - one in Android Preferences and on in a static
> variable, but is a bug now).
> 
> Bug: 919170
> Change-Id: Ia98658cb9d2dc2721b7fef075b2538d65fbe17d5
> Reviewed-on: https://chromium-review.googlesource.com/c/1407076
> Commit-Queue: Peter Conn <peconn@chromium.org>
> Reviewed-by: Pavel Shmakov <pshmakov@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#623723}

TBR=peconn@chromium.org,pshmakov@chromium.org

Change-Id: I4cd1f17109bceb0d6fe1549e15f4654106d15b5a
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 919170
Reviewed-on: https://chromium-review.googlesource.com/c/1418437
Reviewed-by: Shimi Zhang <ctzsm@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#623832}
11 files changed