Support method and field access breakpoints via source editor and Outline view

JDI supports Constructor, Methods entry and exit (normal return or exceptional return) and Field (access and modification) breakpoints. Support these via:

• the source editor
• decompiled .class source editor

However, the best place to support this is via the Outline view. This is because the Outline view shows the structure of the .class files (even if the de-compilation was not possible) as well, not only .java files. Also outline view can support direct and easy setting of these breakpoints.

I am aware of FQCN#method mechanism for adding method breakpoints buy it is not clear how to set this for overloaded methods.

Also CTOR and method breakpoints are useful when the source line numbers do not match the actual compiled class bytecode exactly but is in the neoghborhood.

Überprüfe, wie der Quelltexteditor, der Editor für dekompilierten .class-Quelltext und die Outline view derzeit Java-Elemente und Breakpoints darstellen. Definiere Unterstützung für JDI-Konstruktor-, Methodeneintritts-/Methodenaustritts- und Feldzugriffs-/Feldänderungs-Breakpoints, einschließlich überladener Methoden, wobei die Outline view auch Klassen abdeckt, deren Dekompilierung fehlschlägt; überprüfe das Verhalten in jeder angeforderten Ansicht.