Provide IDE-friendly attributes for detected issues

[ruspl-afed]

For the reported issues it is very important to have:

1. path to the analyzed files
2. start position
3. end position
   Without this information it will be tricky to provide navigation and auto fix. Other consumers should be happy as well, including humans.

[eparovyshnaya]

This part of API is not designed yet.
We have for now

• comment extraction protocol, which currently has only java-implementation (for both block and line comments)
• segment check interface, which does not know the context of the invocation, but reports only type of issues it finds

The third part will bind these two together:

• get a source file for analysis
• extract a comment from it
• run preconfigured segment checks in a particular comment text traversal context (line number)
• for any viable issue type detected by a segment check will issue an actual report entry with all the context we require:

Report::issue(IssueType type, IssueLocation location)

where IssueLocation is aware both of the source file under analysis and the line where the issue takes place. It does not look feasible to provide horizontal positioning in the scope of the line (can be done, but cannot be done easily, thus is not planned at all).

Does it sound promising?