Avoid having two kImageFetcherUmaClientName in chrome/browser/search

In some extreme (non default) jumbo builds, the two
kImageFetcherUmaClientName would end up in the same translation unit and
break those builds. Since they represent two different strings, this
patch gives them unique names.

Bug: 874325
Change-Id: I4f69d78b7ce9f15a9907f6356f21affd506579a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1621177
Auto-Submit: Daniel Bratell <bratell@opera.com>
Reviewed-by: Kyle Milka <kmilka@chromium.org>
Commit-Queue: Daniel Bratell <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#662285}
2 files changed