Address grouping of incidents in webview deviation from initial sort order of issue tree view in sidebar.

[ibolton336]

We have 2 views that show issues, the "Konveyor Issues" tree view and the "Konveyor Analysis View" and the way we group a show the incidents needs to be evaluated and harmonized between them:

See this discussion: #317 (comment)

See roadmap story: https://github.com/konveyor/editor-extensions/blob/fix_relative_dir/docs/roadmap/stories/04-surface_analysis.md

Analysis data comes back it this abbreviated kind of structure (violations == issues):

  "violations": {
    "ruleName-0030": {
      "description": "An example description that can cover all of the incidents included",
      "incidents": [
        {
          "uri": "file://some/file/path",
          "message": "A specific incident message that gives more detail for this incident under this violation",
          "lineNumber": 18
        }
      ]
    }
  }

Under a particular named violation, the incidents can have the same message text. Sometimes there can be multiple groups of incidents under a violation where the message is shared. This happens particularly under a rule like "change package names from javax to jakarta".

So we need to consider:

• Issues have a short description but no message
• Incidents belong to an Issue and have a message
• All of the Incidents under an Issue do NOT have to have the same message
• Showing each Incident's message separately is a waste of space since the message can be identical
• Where can a user ask for a solution? At minimum:
  • Per Incident
  • For a set of Incidents with the same message
  • For all Incidents under an Issue

When display grouped by File, the discussion is much the same.

Asking for a solution can also be at a File level. Lots of options here both in the File grouped view and in the Issue grouped view. The basic solution request command remains the same, just gets invoked at different layers of the Analysis views.