Rename storage-related export macros and build targets

Rename storage-related export macros and build targets

Part of the refactoring effort to consolidate all fileapi/quota/webkit_database/webkit_blob-related code into a single namespace, directory, and component. Discussed here: https://groups.google.com/a/chromium.org/forum/#!topic/storage-dev/aQall8GOrS4

This is itself part of a larger refactoring effort to get rid of the webkit/ directory, as recorded in the following bug:

BUG=338338
TBR=darin@chromium.org

Committed: https://crrev.com/fa309edf9033cf74f2aa971cb4284d6849b7bc1a
Cr-Commit-Position: refs/heads/master@{#291718}

[tzik, 2014-08-25 17:37:12]

lgtm

[pilgrim_google, 2014-08-25 17:40:18]

The CQ bit was checked by pilgrim@chromium.org

[commit-bot: I haz the power, 2014-08-25 17:41:03]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/pilgrim@chromium.org/498273002/1

[darin (slow to review), 2014-08-25 18:24:19]

I'm a little confused by the renaming of webkit_storage_browser_export.h to
storage_export.h. Should it keep the "browser" bit since there is still a
storage_common_export.h? (No need to slow down this CL, but just curious where
this is headed.)

[darin (slow to review), 2014-08-25 18:24:27]

LGTM

[commit-bot: I haz the power, 2014-08-25 18:25:34]

Committed patchset #1 (1) as 7bb52bec29ac3128e6604970f38b648423239299

[pilgrim_google, 2014-08-25 19:40:16]

On 2014/08/25 18:24:19, darin wrote:
> I'm a little confused by the renaming of webkit_storage_browser_export.h to
> storage_export.h. Should it keep the "browser" bit since there is still a
> storage_common_export.h? (No need to slow down this CL, but just curious where
> this is headed.)

Next CL will collapse those into one.

[commit-bot: I haz the power, 2014-09-10 02:35:50]

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