Change overload naming algorithm

We agree that current !overload-1 is weird, so I suggest a change:

interface mixin Foo {
  void overload(); // this should be just foo-overload
  void overload(short s); // foo-overload-s
  void overload(long s); // foo-overload-s-1
  void overload(DOMString str, object obj); // foo-overload-str-obj
};

Basically we name the operations by its argument names, and if some of them collides, then attach -(counter).

@marcoscaceres and @sidvishnoi, what do you think?

No implementation files or tests are named in the issue. Start by locating the current WebIDL overload naming implementation and its tests, then compare the existing output with the examples in the issue; done means argument-based names are generated and collisions receive sequential counters.