Methods added in our proxies should have more complex names

I recently ran into this SO question where user had a method with same signature as one we add on our proxies (leading to DuplicateMemberException).

This got me thinking whether we shouldn't use some more obscure method names for whatever we add on proxies. E.g. each such method having some prefix such as weld__<methodName>.

It's not the first time I've seen someone bump into this issue but it's still rare hence this is not really an issue but enhancement and with low priority (if it's even worth the effort).
Theoretically speaking we shouldn't break anything by changing it as this is all a matter of Weld internals, but we may want to double check with at least integrators (WFLY and other servers) as they often incorrectly depend in our internals.