Roll Catapult from 503f81b8fe09 to ae2ed9f992e1 (3 revisions)

https://chromium.googlesource.com/catapult.git/+log/503f81b8fe09..ae2ed9f992e1

2020-05-20 sadrul@chromium.org Revert "[Telemetry] Add LocalFirstBinaryManager"
2020-05-20 fancl@chromium.org sheriff-config: Increase per instance resources
2020-05-20 bsheedy@chromium.org [Telemetry] Add LocalFirstBinaryManager

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC sadrul@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: chromium:1054583
Tbr: sadrul@google.com
Change-Id: I9ca69e4918353a651f41dee0367fcee5ea85dccf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2210648Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#770762}

DEPS

@@ -241,7 +241,7 @@ vars = {
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling catapult
   # and whatever else without interference from each other.
-  'catapult_revision': '503f81b8fe09ed0850144493713ad66bd72620fd',
+  'catapult_revision': 'ae2ed9f992e1ccbf4e2bebf0c083ddc0e81a1213',
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling libFuzzer
   # and whatever else without interference from each other.