Orderfile: Added performance and memory evaluation to the orderfile pipeline

After the generation of the new orderfile, we build two non-instrumented
version of chrome with and without orderfile. We then run benchmarks on each
build. Speedometer2.0 is used to assess the performance.  For memory, we
created orderfile.memory_mobile to evaluate the native code memory footprint.
The results are then added to the JSON output.

Bug: 947012
Change-Id: If316e63ef1a50a6d9a6ef0c97200d36035e7640d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1543489
Commit-Queue: Monica Basta <msalama@google.com>
Reviewed-by: Matthew Cary <mattcary@chromium.org>
Reviewed-by: Hector Dearman <hjd@chromium.org>
Reviewed-by: Benoit L <lizeb@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#653978}

• base/android/library_loader/library_prefetcher.cc[diff]
• services/resource_coordinator/memory_instrumentation/queued_request_dispatcher.cc[diff]
• tools/cygprofile/orderfile_generator_backend.py[diff]
• tools/perf/contrib/orderfile/orderfile.py[diff]