Replace looseSignature with a better and fine grained annotation

[utzcoz]

If one method of a shadow class uses the Class that brought by newer SDK than user's compileSdk, and it will cause compiling error for user because Robolectri's Shadows loads this shadow class, and trigger this shadow class to load this new Class. In previous experience, we use looseSignatures to mark shadow class and use Object to replace all input parameters of this method to avoid compiling error and ensure ShadowWrangle can find this method. looseSignatures work fine now, but it's coarse-grained. ClassName can be used to mark the input parameter that has new Class type only, and ShadowWrangle will provide type checking for real input parameter to ensure real passed input parameters match to expected class types.

Close #6888.

Moved from #7770 with a correct branch name.

[utzcoz]

@hoisie It's first round prototype now. I make building and all tests passed with current migrations. At least it can work with standard looseSignature methods, including standard class, internal class, collections with generic, array type, return types. I still work #8841 to try to reduce looseSignature usage occasion for one shadow method for different SDKs as they return different types.

Actually, current implementation has other limitations, but I think it can be reviewed and discussed now. I can continue the improvement based on the first round review suggestions.