Goal:

• Information about packages is stored in the request in a form of a flat list of package names. This means that there is no package description not information about package repository. When editing a blueprint information about the package gets rendered as "Not available"
• The goal is to be able to render package summary and repository

Acceptance Criteria:

• Package description gets rendered on Edit
• Package repository gets rendered on Edit

Open questions:

• Should we try to resolve the data in frontend or can we store it in the blueprint request?
• Is it possible to accurately store the repository information without depsolving?