With things like:

https://bugs.chromium.org/p/chromium/issues/detail?id=589887

and occasional bad C++ stackwalking the JNI / NON-JNI tag seems more trouble than they are useful.

To avoid possible bad bucketing lets just remove that label from the signature altogether. We can have a separate field in the protobuffer / crash UI denoted to JNI/NON-JNI-ness.