Move add/removeEventListener() to custom bindings

Move add/removeEventListener() to custom bindings

This is to prepare for measuring the impact of throwing an exception
when these functions are called with < 2 arguments, as per spec. This
has to be done by either tweaking the bindings generator or in custom
bindings, and since this is temporary custom bindings seem better.

This CL merely copies the generated bindings to custom bindings, with
the minimal changes needed for it to compile. A follow-up CL will add
the actual use counters.

BUG=353484

[philipj_slow, 2015-07-09 22:07:03]

The CQ bit was checked by philipj@opera.com to run a CQ dry run

[commit-bot: I haz the power, 2015-07-09 22:08:04]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1227823009/1

[philipj_slow, 2015-07-09 22:08:37]

philipj@opera.com changed reviewers:
+ haraken@chromium.org

[philipj_slow, 2015-07-09 22:08:38]

PTAL, and please advise if you see a better way to get the use counter data we
need to make the required change.

Followed by https://codereview.chromium.org/1233483002

[commit-bot: I haz the power, 2015-07-09 23:25:30]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-07-09 23:25:32]

Dry run: This issue passed the CQ dry run.

[haraken, 2015-07-09 23:37:52]

Maybe would it be worth adding [Custom=CallPrologue] (just like
[Custom=CallEpilogue])? Then we can throw an exception in the prologue.

[philipj_slow, 2015-07-10 07:41:20]

On 2015/07/09 23:37:52, haraken wrote:
> Maybe would it be worth adding [Custom=CallPrologue] (just like
> [Custom=CallEpilogue])? Then we can throw an exception in the prologue.

An excellent suggestion, thank you! I'll do that in the other CL and close this
one.