Suggestion: add troubleshooting tools

[alexblack]

The Parse SDK suffers from bugs that are hard to reproduce, for example #267, #218, #209, #203 (these are just issues I have been involved with). To quote the parse team:

Unfortunately this seems like an impossible scenario for me, so I'm not entirely sure how this could happen or even reproduce it.

At the same time, the Parse team takes the stance that if the 3rd party person who found the Parse bug cannot figure out how to reproduce it, then they will not investigate.

This means Parse never fixes their bugs (for example #203 was first filed June 4th 2015, over 7 months ago). I'd like to suggest that Parse add some code to the SDK to aid in these situations. Suggestions include (but are not limited to):

1. A simple method to capture and upload the Parse local data store (LDS), eg Parse.uploadLDSToParse(String id), or Parse.uploadLDSTo3rdParty(String urlToPostTo);
2. A simple method to capture recent log statements from parse and upload
3. More detail included in exceptions, eg "ParseUser$State java.lang.ClassCastException: org.json.JSONObject$1 cannot be cast to java.lang.String" if we knew what the JSONObject$ was then we might have some insight.
4. Include an ID (or GUID) with each exception that can be traced back to the server request, so when users submit a stack trace Parse staff can simply lookup the server request associated with the exception (if there was one)
5. A method to clear things out when they get into a bad state, eg when Parse puts a JSONObject in where it expects a String value.