Do not invalidate binding an interface if a static method cannot be bound

[gugavaro]

Currently .Net has a limitation for Actions and Functions to support up to 16 arguments.
When generator hits a case where method has more than 16 arguments it will skip it after providing a warning.

EXEC : warning BG8D00: More than 16 parameters were found, which goes beyond the maximum number of parameters. (in method Of in managed type Java.Util.IMap)

The problem is that after ignoring the issue, Generator also invalidate the whole type because it contains invalid methods.

EXEC : warning BG8503: Invalidating Java.Util.IMap and all nested types because some of its methods were invalid.

We are hitting this case when trying to bind some static methods on Interface java.util.Map<K, V>

https://developer.android.com/reference/java/util/Map#of(K,%20V,%20K,%20V,%20K,%20V,%20K,%20V,%20K,%20V,%20K,%20V,%20K,%20V,%20K,%20V,%20K,%20V,%20K,%20V)

We need to not treat those warning as warning since it causes us problems later.
When dealing with methods that have more than 16 arguments, we may need to create our own type/delegate.

[jpobst]

To clarify, I believe the issue here is we do not need to invalidate the interface if we cannot bind a static or default method, as these are not required to be implemented by the user in order to implement the interface.

[jpobst]

After further research, we do handle default correctly, but not static.