[Java.Interop] Verify JniPeerMembers managedPeerType parameter.

Commit b754516 fixed an issue wherein the JniPeerMembers
managedPeerType parameter didn't match the type declaring the
JniPeerMembers parameter (which would result in "broken"
JniPeerMembers.InstanceMethods.Call*Method() behavior as the
virtual-vs.-nonvirtual type check would fail), and asks:

> (I wonder if there's a way to check/assert for this...)

Yes, there is a way: use JavaVM.GetJniTypeInfoForType() and see if
JniTypeInfo.JniTypeName matches the jniPeerType value.

Add a Debug.Assert() to ensure that this is true.

Note: Why Debug.Assert() and not ArgumentException? Because I only
want to have this extra checking occur in Debug builds, not Release
builds. This may be a mistake...especially since Debug.Assert() only
logs to TestOutput-<AssembyName>.txt, and doesn't throw an exception
or abort the process, and now that I look for the assert messages I
see a great many of them in the log file...

Author: jonpryor

src/Java.Interop/Java.Interop/JniPeerMembers.cs

@@ -1,4 +1,5 @@
 using System;
+using System.Diagnostics;
 using System.Collections.Generic;
 
 namespace Java.Interop {
@@ -14,6 +15,13 @@ public JniPeerMembers (string jniPeerType, Type managedPeerType)
 			if (!typeof (IJavaObject).IsAssignableFrom (managedPeerType))
 				throw new ArgumentException ("'managedPeerType' must implement the IJavaObject interface.", "managedPeerType");
 
+			Debug.Assert (
+					JniEnvironment.Current.JavaVM.GetJniTypeInfoForType (managedPeerType).JniTypeName == jniPeerType,
+					string.Format ("ManagedPeerType <=> JniTypeName Mismatch! javaVM.GetJniTypeInfoForType(typeof({0})).JniTypeName=\"{1}\" != \"{2}\"",
+						managedPeerType.FullName,
+						JniEnvironment.Current.JavaVM.GetJniTypeInfoForType (managedPeerType).JniTypeName,
+						jniPeerType));
+
 			JniPeerTypeName = jniPeerType;
 			ManagedPeerType = managedPeerType;
 			instanceMethods = new JniPeerInstanceMethods (this);