Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

Review URL:

Cr-Original-Commit-Position: refs/heads/master@{#378309}
Cr-Mirrored-Commit: 2a28406877d06cc4d7511295067c6be031e70e9d
2 files changed