Correct the way Weld chooses proxy packages for signed classes

Continuation of WELD-2402 - we found out that the fix was only partial and introduced problems in existing applications which relied on package private access in signed packages with proxies.

All proxies of signed classes can be placed in original packages except for those where bean types of proxied bean equal to Object.class.
The reason why it can be the same package is that Weld re-uses the ProtectionDomain of the proxied bean type for newly created proxy - that way the signers of that class will effectively remain the same.