Enable more benchmark_smoke_unittest coverage

Enable more benchmark_smoke_unittest coverage

Previously, benchmark_smoke_unittest has a heuristic to pick
a benchmark for smoke testing if the benchmark uses a test
in measurement directory.
This patch removes that check, and instead provide a black
list of benchmarks module that we exclude the
benchmark_smoke_unittest to avoid high CQ time.

This helped increases benchmark smoke coverage from 14 benchmarks -> 33 benchmarks (one in each benchmark module).

On my local linux machine, this increases the cycle time of
benchmark_smoke_unittest from 20s -> 1m7s.

BUG=490130
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_perf_bisect;tryserver.chromium.perf:android_nexus5_perf_bisect

Committed: https://crrev.com/65014162e48a7f5881e8b282dd9e8dc17c5aa7c4
Cr-Commit-Position: refs/heads/master@{#330909}

[nednguyen, 2015-05-20 20:13:10]

Patchset #1 (id:1) has been deleted

[nednguyen, 2015-05-20 20:13:15]

Patchset #1 (id:20001) has been deleted

[nednguyen, 2015-05-20 20:13:23]

Patchset #1 (id:20001) has been deleted

[nednguyen, 2015-05-20 20:28:24]

nednguyen@google.com changed reviewers:
+ dtu@chromium.org, sullivan@chromium.org

[dtu, 2015-05-20 21:01:39]

lgtm

[nednguyen, 2015-05-20 23:29:01]

The CQ bit was checked by nednguyen@google.com

[nednguyen, 2015-05-20 23:29:01]

The patchset sent to the CQ was uploaded after l-g-t-m from dtu@chromium.org
Link to the patchset: https://codereview.chromium.org/1144193002/#ps80001
(title: "Black list blink_perf")

[commit-bot: I haz the power, 2015-05-20 23:31:30]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1144193002/80001

[commit-bot: I haz the power, 2015-05-21 01:33:40]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-05-21 01:33:43]

Try jobs failed on following builders:
  win_perf_bisect on tryserver.chromium.perf (JOB_TIMED_OUT, no build URL)

[nednguyen, 2015-05-21 01:34:09]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2015-05-21 01:36:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1144193002/80001

[commit-bot: I haz the power, 2015-05-21 04:20:41]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-05-21 04:20:42]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[nednguyen, 2015-05-21 05:49:09]

The CQ bit was checked by nednguyen@google.com

[nednguyen, 2015-05-21 05:49:10]

The patchset sent to the CQ was uploaded after l-g-t-m from dtu@chromium.org
Link to the patchset: https://codereview.chromium.org/1144193002/#ps100001
(title: "Blacklist dom_perf instead of blink_perf")

[commit-bot: I haz the power, 2015-05-21 05:49:21]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1144193002/100001

[commit-bot: I haz the power, 2015-05-21 07:07:30]

Committed patchset #4 (id:100001)

[commit-bot: I haz the power, 2015-05-21 07:08:32]

Patchset 4 (id:??) landed as
https://crrev.com/65014162e48a7f5881e8b282dd9e8dc17c5aa7c4
Cr-Commit-Position: refs/heads/master@{#330909}

[battre, 2015-05-21 10:00:00]

A revert of this CL (patchset #4 id:100001) has been created in
https://codereview.chromium.org/1143363006/ by battre@chromium.org.

The reason for reverting is: Reverting due to flaky perf tests (see
crbug.com/490130 for details)..