Combine storage_browser_export.h and storage_common_export.h

Combine storage_browser_export.h and storage_common_export.h

BUG=338338
TBR=darin@chromium.org

Committed: https://crrev.com/0363f2c67015888f402bae71239c9163ad9ae031
Cr-Commit-Position: refs/heads/master@{#292435}

[pilgrim_google, 2014-08-28 15:28:52]

pilgrim@chromium.org changed reviewers:
+ jam@chromium.org, jamesr@chromium.org

[pilgrim_google, 2014-08-28 17:21:12]

The CQ bit was checked by pilgrim@chromium.org

[commit-bot: I haz the power, 2014-08-28 17:22:22]

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

[commit-bot: I haz the power, 2014-08-28 18:08:26]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_chromium_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[jamesr, 2014-08-28 18:26:22]

How will calls from the webkit/browser/storage DLL to the webkit/common/storage
DLL work in the component build on windows?  Since STORAGE_IMPLEMENTATION is set
on both sides won't the declspec be wrong?

[jamesr, 2014-08-28 18:59:56]

https://codereview.chromium.org/512253002/diff/1/webkit/storage_browser.gyp
File webkit/storage_browser.gyp (left):

https://codereview.chromium.org/512253002/diff/1/webkit/storage_browser.gyp#o...
webkit/storage_browser.gyp:29: 'browser/storage_export.h',
this target should list whatever export header it's using in the sources list

[commit-bot: I haz the power, 2014-08-28 19:05:14]

Committed patchset #1 (id:1) as b5402ee22d7dc6abd27b132fdd3880f8ff61027e

[commit-bot: I haz the power, 2014-09-10 03:01:18]

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