[critical] Improve lambda breakpoints when using gradle build server

[gayanper]

When using gradle build server, the lambda method name tends to change on large file which I'm not sure of the reason which I have not looked into Java Language Spec on how lambda method names are computed.

What was observed is the method name has the format classMethodName$lambda$#. This cause method name mismatches due to the JDT method name and JDI method name is different.

[gayanper]

@testforstephen could we use the source location information of the method or something similar to narrow down the method to match signature instead of using the name ? Not using the name could resolve this issue.

[testforstephen]

gradle build server uses the javac to compile the code, which may use different rules to name the generated classes. Do you have a concrete use case to explain the issue further?