Issue 1197 - change local copy of v8 (to 4.3.15) to work with Visual Studio 2013

# it cannot be linked for android.

- add gyp 'host_arch' variable which is now required
- generate MSVS solution and projects for MSVS2013
- change to work with new signature of callback functions
- add helper AdblockPlus::Utils::ThrowException to throw js exceptions (it's used in callbacks).
- change to take into account renaming of v8::Persistent to v8::UniquePersistent
- add initializing of v8 platform and link with the static lib v8_libplatform.
- fix IdleNotification because 'v8::V8::IdleNotification' is not available anymore, we have to use 'isolate->IdleNotification(1000)'
- pass isolate argument when it's necessary

# depends on
# https://codereview.adblockplus.org/6233220328718336/ - Issue 1197- fix isolate management
#     https://codereview.adblockplus.org/5145227803230208/ - Issue 1197 - adapt gyp variables
#     https://codereview.adblockplus.org/5117069997637632/ - Issue 1548 - manually disable usage of v8_random_seed in gyp

[sergei, 2015-06-11 13:29:08]

Felix or Wladimir, could someone of you update our v8 repository and gyp
repository. Pay attention, that v8 had been migrated to git and they changed
hashes (more infor on
https://groups.google.com/forum/#!topic/v8-users/VgL3Fn4ijqE).

[Eric, 2016-01-25 14:07:16]

Since I've been added as a reviewer, a few things are obvious just from the
review title and description:

1) This needs its own ticket for libadblockplus and should not reuse IE ticket
#1197. When we update v8, we're not doing it solely for Visual Studio version,
or even just for IE. We're doing it to stay current. Issue #1197 depends on the
current one, but isn't the same.

2) The presence of changes for "createsolution.bat" belongs in a separate change
set for IE specifically. We also need to change the build instructions. We
should probably also update to the VS 2015 toolset which is now available. (I
don't think we'll need to compile libadblockplus in C++03 mode, but that needs
testing before commit.) All these concerns, however, have nothing to do with
updating v8.

3) The version number of v8 to which we're updating needs to be in both the
title of the issue description and the title of this review. That version number
is too important to be buried in the description.

[sergei, 2016-01-25 15:16:11]

I will rebase and update this review after getting of LGTM for the dependencies.

On 2016/01/25 14:07:16, Eric wrote:
> Since I've been added as a reviewer, a few things are obvious just from the
> review title and description:
> 
> 1) This needs its own ticket for libadblockplus and should not reuse IE ticket
> #1197.
#1197 is libadblockplus ticket, it does not reuse IE ticket, doesn't it?

> When we update v8, we're not doing it solely for Visual Studio version,
> or even just for IE. We're doing it to stay current. Issue #1197 depends on
the
> current one, but isn't the same.
It's very important to say that we are updating v8 not only to stay current but
also to have it working with Visual Studio 2013. It's the reason it's not
updated to the latest version. It took a quite long time to find those spicific
commit to which we can update it now.

> 
> 2) The presence of changes for "createsolution.bat" belongs in a separate
change
> set for IE specifically.
For IE specifically it will be in a review for IE repository for the change with
update of libadblockplus.
> We also need to change the build instructions. We
> should probably also update to the VS 2015 toolset which is now available. (I
> don't think we'll need to compile libadblockplus in C++03 mode, but that needs
> testing before commit.) All these concerns, however, have nothing to do with
> updating v8.
Good point. It should be indeed in a separate commit, however the change
2012->2013 in README.md should be made here.
It won't be possible to compile it in C++-03 mode because v8 requries some C++11
feature.

> 
> 3) The version number of v8 to which we're updating needs to be in both the
> title of the issue description and the title of this review. That version
number
> is too important to be buried in the description.
Done.

[Eric, 2016-01-25 16:02:49]

On 2016/01/25 15:16:11, sergei wrote:
> #1197 is libadblockplus ticket, it does not reuse IE ticket, doesn't it?

I had forgotten the details myself.

#1197 is the libadblockplus ticket to get v8 to compile with C++11 (somehow).
The decision is to do that by upgrading v8 to a newer version.

#1087 is the ABP-IE ticket to upgrade from VS 2012 to VS 2013.

> It's very important to say that we are updating v8 not only to stay current
but
> also to have it working with Visual Studio 2013. It's the reason it's not
> updated to the latest version. It took a quite long time to find those
spicific
> commit to which we can update it now.

Please distinguish between "what we're doing" and "why we're doing it". "What
we're doing" belongs in the title. "Why we're doing it" belongs in the
documentation (the commit message in this case).

> For IE specifically it will be in a review for IE repository for the change
with
> update of libadblockplus.
[...]
> It should be indeed in a separate commit, however the change
> 2012->2013 in README.md should be made here.

All of the IE-specific changes belong in change set labelled #1087.

FYI, I've just updated #1087 to require VS 2015.

> It won't be possible to compile it in C++-03 mode because v8 requries some
C++11
> feature.

I've seen a number of comments from Felix in the past about staying in C++03
(for reasons I didn't know). I'm perfectly pleased not to stay in the past.