define public_key_hashes to be the same order as the verified cert chain

CertVerifyResult and SSLInfo have a public_key_hashes member which was
previously defined as being in an arbitrary order. Change the
definition to require the order matches that of the verified cert
chain, which simplifies the usage of the member. (And some uses
already interpreted it as matching the cert chain order, despite the
old definition allowing it to be in arbitrary order.)

NO_IFTTT=change to comment & requirements, but doesn't change the type or ipc encoding

Bug: 41286522
Change-Id: I877642757aa228721f2f7db0c812961d33552524
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6756818
Reviewed-by: Nick Harper <nharper@chromium.org>
Commit-Queue: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1489099}