GitLab

This changes ContentVerifier::ShouldVerifyAnyPath to work with
relative paths, instead of constructing full paths.

This should help in using "canonical" paths in content verifier
code. "canonical" paths shouldn't be used as full paths as it
isn't safe to to do so on windows. Canonicalization lowercases
paths on windows, but for full paths with drive letters, that
doesn't seem immediately right. So this CL just make the
code in question work with relative paths, which shouldn't
need to worry about these caveats.

Also, fullpath length is strictly larger than relative path, this
gives marginal win.

Bug: 796395
Test: No behavior changes expected.
Change-Id: I924768805a61726f04ab4c1d64880fb326d8bf47
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2035497Reviewed-by: Oleg Davydov <burunduk@chromium.org>
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#739409}