Parse additional dex files created in uncommon way

[crazyformat]

One build tool - Buck (http://buck.build) is using uncommon approach for multidex. It is packing
additional dex files not as classesX.dex but as a pack of .jar files in assets/secondary-program-dex-jars.
This diff adds support for this approach allowing parsing of these files along with common classesX.dex.

Minors:
 - no need to print non-unique test names. This should not happen in common but some apks somehow have it
 - filter out common example test name "testFoo"

[crazyformat]

Thanks for looking into this. You've raised absolutely reasonable concerns. I'm not happy with neither of changes. Buck behavior is not documented anywhere, that's how apks look like but I was not able to find any examples or documentation anywhere (not even in our internal documentation :( ). "testFoo" is another bad idea that I'm not happy about..

All together, I don't think we should move on with this pull-request. Thanks again and sorry for wasting your time.

By the end of the day I had to move away from dex-test-parser because in some cases it is still not able to find all the instrumentation tests in the APK, there is just no evidence of some test methods in any of dex files. Apparently, we have some in-flight generated test methods.