Enable automatic management of cloned templates (or not)

[marmarta]

The problem you're addressing (if any)

If a user installs a template with qvm-template-gui and clones them, the template won't appear in qvm-template-gui, and maybe it should? It would be convenient to actually manage all templates in one place.

The solution you'd like

Unify template management for those coming from qvm-template and their clones.

The value to a user, and who that user might be

Simpler template management.

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)

[ben-grande]

qvm-template-gui is useful to install, upgrade(reinstall) and remove templates coming from the repositories or from the initial install (local package).

If the template is cloned or restored from backup, what can qvm-template-gui for that template besides removing it? It cannot install it as it is not registered in a repo, it cannot upgrade as it is not a package, it could only remove that template, which Qubes Manager can already do that for templates and other qube types.

[marmarta]

I'd like it to at least show the template, show information about whether it's cloned, from what, whether it's obsolete - mostly to avoid situation in which someone forgets about a template because it's not in the template-gui.