Roll src/third_party/catapult/ 35cefb8d8..0273fdc65 (3 commits)

https://chromium.googlesource.com/catapult.git/+log/35cefb8d8a2f..0273fdc65acb

$ git log 35cefb8d8..0273fdc65 --date=short --no-merges --format='%ad %ae %s'
2018-05-15 sullivan Move auto_triage to mark_recovered_alerts and correct logic.
2018-05-14 simonhatch Dashboard - Remove TestMetadata.monitored
2018-05-14 maxlg [CSMMerging] Refactor breakdown_tree_helper with findEmptyRangesBetweenRanges

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=sullivan@chromium.org

Change-Id: I335c37e39c62372c30aac7bf4d9076e18812fc61
Reviewed-on: https://chromium-review.googlesource.com/1060103Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#558808}

DEPS

@@ -156,7 +156,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': '35cefb8d8a2fde1e2506a3688d6fce3825387fea',
+  'catapult_revision': '0273fdc65acbdf93397ca6f7b6c3d1a9f8152079',
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling libFuzzer
   # and whatever else without interference from each other.