Use unique testcase name for tests.
Use unique testcase name for tests.

When all tests are linked together (e.g. the 'unit_tests' build target),
googletest requires that each unit test have a unique name, but sees
PerfDataFiles from both perf_reader_test.cc and perf_serializer_test.cc. Using
a unique (but repetitive!) testcase name is a stopgap measure until each unit
test is built separately (e.g. separate bazel cc_test() targets).

PiperOrigin-RevId: 185462487

google/perf_data_converter,google/perf_data_converter,google/perf_data_converter