Clean up incorrect V8_DEPRECATION macro usage and enable deprecatitions

Clean up incorrect V8_DEPRECATION macro usage and enable deprecatitions

We turn the default for standalone builds on, however, I added overrides
to all targets to turn it locally off again. In follow up CLs, I'll
clean up one target at a time.

BUG=v8:3023
R=dcarney@chromium.org, machenbach@chromium.org
LOG=n

Committed: https://code.google.com/p/v8/source/detail?r=18002

[jochen (gone - plz use gerrit), 2013-11-22 09:37:33]

plz review

[dcarney, 2013-11-22 09:45:07]

lgtm

[Michael Achenbach, 2013-11-22 10:14:12]

https://codereview.chromium.org/82763004/diff/90001/build/standalone.gypi
File build/standalone.gypi (right):

https://codereview.chromium.org/82763004/diff/90001/build/standalone.gypi#new...
build/standalone.gypi:40: 'v8_deprecation_warnings': 1,
Does that not need a % to be overwritable?

[jochen (gone - plz use gerrit), 2013-11-22 10:19:18]

https://codereview.chromium.org/82763004/diff/90001/build/standalone.gypi
File build/standalone.gypi (right):

https://codereview.chromium.org/82763004/diff/90001/build/standalone.gypi#new...
build/standalone.gypi:40: 'v8_deprecation_warnings': 1,
On 2013/11/22 10:14:13, machenbach wrote:
> Does that not need a % to be overwritable?

the default in features.gypi is 0. If I make this overwritable, it'll just be
ignored.

[Michael Achenbach, 2013-11-22 10:54:23]

lgtm

[jochen (gone - plz use gerrit), 2013-11-22 10:58:03]

Committed patchset #1 manually as r18002 (presubmit successful).