We can't show rich text in the package list, because the we use the onLineLaidOut signal there, which doesn't work with Rich Text. So for the package list we should NOT use the formatted version of the description because that will contain ugly HTML tags that the user wouldn't want to see. Show the original description there. Use the formatted description only in the detail page where we don't use onLineLaidOut.
Contributes to issue CURA-8565.
It's the same, but it's a bit easier to read what it's doing. Placing the package type check first also helps to read what the two cases are here.
Contributes to issue CURA-8562.
Materials can be certified, while plugins can be verified.
Added packageType to the model such that the card knows which icon
to use.
Contributes to CURA-8562
The previous implementation added a section_title to the package_info
which was also stored in the packages.json. The section_title is now
provided to the PackageModel as an extra optional argument.
Contributes to CURA-8558
By providing a `section_title` with a string to the `package_data`
packages can be subdivided in sections, each with its own header.
For remote packages this will be `None` and therefore no sections are
created there.
Contributes to CURA-8558
