Define crash keys in the directory hierarchy where they are used.

Define crash keys in the directory hierarchy where they are used.

Currently, fixed crash keys are (for the most part) all defined in one
large array in //chrome/common/crash_keys.cc. This leads to problems
where users of crash will need to manually keep in sync with various
changes to the active crash keys.

Instead, fixed crash keys will be defined in the directory hierarchy
where they're used (ie. //content, //media, etc...), and a new
"Append<$COMPONENT>CrashKeys() function will be provided so that it's
easy to get all keys for that component.

Also, while at it, remove some unused crash keys.

BUG=598854

[halliwell, 2016-04-22 02:11:50]

Description was changed from

==========
Define crash keys in the directory hierarchy where they are used.

Currently, fixed crash keys are (for the most part) all defined in one
large array in //chrome/common/crash_keys.cc. This leads to problems
where users of crash will need to manually keep in sync with various
changes to the active crash keys.

Instead, fixed crash keys will be defined in the directory hierarchy
where they're used (ie. //content, //media, etc...), and a new
"Append<$COMPONENT>CrashKeys() function will be provided so that it's
easy to get all keys for that component.

Also, while at it, remove some unused crash keys.

BUG=598854
==========

to

==========
Define crash keys in the directory hierarchy where they are used.

Currently, fixed crash keys are (for the most part) all defined in one
large array in //chrome/common/crash_keys.cc. This leads to problems
where users of crash will need to manually keep in sync with various
changes to the active crash keys.

Instead, fixed crash keys will be defined in the directory hierarchy
where they're used (ie. //content, //media, etc...), and a new
"Append<$COMPONENT>CrashKeys() function will be provided so that it's
easy to get all keys for that component.

Also, while at it, remove some unused crash keys.

BUG=598854
==========

[halliwell, 2016-04-22 02:12:42]

The CQ bit was checked by halliwell@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-04-22 02:13:14]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1849413003/190001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1849413003/190001

[commit-bot: I haz the power, 2016-04-22 02:15:50]

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

[commit-bot: I haz the power, 2016-04-22 02:15:51]

Dry run: Try jobs failed on following builders:
  ios_dbg_simulator_gn on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_dbg_simulator_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_rel_device_gn on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_gn...)
  ios_rel_device_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)
  mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)