[Telemetry] Explicitly define Name() method for all perf benchmarks

[Telemetry] Explicitly define Name() method for all perf benchmarks.

To make sure that this does not change any existing benchmarks' names, I
added a test in benchmark_unittest.

BUG=446891
Committed: https://crrev.com/32006f3b29ab4c5f2a0f43aa9f0d34511c0cfdbb
Cr-Commit-Position: refs/heads/master@{#311807}

[nednguyen, 2015-01-15 15:47:37]

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

[dtu, 2015-01-15 21:27:23]

lgtm

https://codereview.chromium.org/816353008/diff/1/tools/perf/benchmarks/benchm...
File tools/perf/benchmarks/benchmark_unittest.py (right):

https://codereview.chromium.org/816353008/diff/1/tools/perf/benchmarks/benchm...
tools/perf/benchmarks/benchmark_unittest.py:54: class
TestPerfBenchmarkNames(unittest.TestCase):
Do you even want to check in this check? Just running it locally is enough,
right?

[nednguyen, 2015-01-15 21:39:02]

On 2015/01/15 21:27:23, dtu wrote:
> lgtm
> 
>
https://codereview.chromium.org/816353008/diff/1/tools/perf/benchmarks/benchm...
> File tools/perf/benchmarks/benchmark_unittest.py (right):
> 
>
https://codereview.chromium.org/816353008/diff/1/tools/perf/benchmarks/benchm...
> tools/perf/benchmarks/benchmark_unittest.py:54: class
> TestPerfBenchmarkNames(unittest.TestCase):
> Do you even want to check in this check? Just running it locally is enough,
> right?

Let's just keep it here to make sure that for the time from now until we change
the implementation of "Name" in benchmark.py, noone introduces new benchmark
without explicitly defining its name.

[nednguyen, 2015-01-15 21:39:06]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2015-01-15 21:41:13]

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

[commit-bot: I haz the power, 2015-01-15 23:54:30]

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

[commit-bot: I haz the power, 2015-01-15 23:54:31]

Try jobs failed on following builders:
  android_dbg_tests_recipe on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_dbg_tes...)

[nednguyen, 2015-01-16 00:41:37]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2015-01-16 00:43:02]

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

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

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-01-16 01:22:33]

Patchset 1 (id:??) landed as
https://crrev.com/32006f3b29ab4c5f2a0f43aa9f0d34511c0cfdbb
Cr-Commit-Position: refs/heads/master@{#311807}