Improved grok patterns for Java

I used logstash to parse our log files. Unfortunately this parsing failed for some special named classes and methods.

We allow the underscore character to be part of the package or the class name. This is not allowed in the grok pattern for Java classes. So I added this character to the JAVACLASS pattern.

Furthermore I have log lines containing the constructor of classes as method, which is logged as "<init>". So I introduced the grok pattern for a Java method that allows additionally to the WORD pattern the angle brackets und used that pattern in the JAVASTACKTRACEPART pattern.
@kleini Hello Marcus, I'm reviewing for myself the pending change on Java pattern, but I do not understand your proposal for JAVAMETHOD, why do you add the < and > characters ?
Did you actually encountered them in a stacktrace, could you give an example please ?