[EPIC] Have clustered advise outputs

[Gkrumbach07]

Problem statement

As a user of Thoth adviser, I want to be able to sort and filter through the justifications provided after an advise so that I can find display only the information that is relevant to me.

High-level Goals

• Justifications and stack info can be grouped into smaller categories
• Justifications and stack info can have varying levels of visibility.

Proposal description

I want to be able to filter or sort my advise output's justifications and stack info by category and priority through Thamos.

Additional context

For example the justification bellow can have labels attached such as: labels: ["environment", "parameter"]

{
    "link": "https://thoth-station.ninja/j/env",
    "message": "No CUDA used",
    "type": "INFO"
}

This can be queried in an advise, so a user can get all environment justifications.

Acceptance Criteria

• [x] explore which justifications can be clustered easily (scorecards? actionable items?)
• [ ] https://github.com/thoth-station/adviser/issues/2180
• [x] https://github.com/thoth-station/thamos/issues/1118
• [x] https://github.com/thoth-station/thamos/issues/1129
• [ ] extend this clustering for horus and jupyerlab-extension

[Gkrumbach07]

/sig user-experience /priority important-longterm

[codificat]

/transfer core

[sesheta]

@Gkrumbach07: This issue is currently awaiting triage. If a refinement session determines this is a relevant issue, it will accept the issue by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Gkrumbach07]

Justifications that can be clustered easily

• scorecards
• environment parameters set or not set
• solver rules
• installation errors / solver did not solve specific version of package
• external links
• cve info

Each of these groups have seen abundantly in the justification or stack info list. They all can be easily be identified as groups by the pattern of the text.