Split deep scan failures and incorrect password prompts

Right now, an incorrect password prompt is counted as a deep scan
failure. This may be technically accurate, as the file was not
successfully scanned, but it does not help to understand trends in deep
scanning performance. This CL splits the two buckets for a more
understandable metric.

This CL also adds a new histogram to log whether the incorrect password
result came from the client or the server.

Bug: 316231665
Change-Id: Ie5d1ca24a3ee7c4c180ca66997fe3bc0d9e333af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5362691
Reviewed-by: Xinghui Lu <xinghuilu@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1271739}