`onyo new -t` works for templates, and yaml outside of onyo, but not normal assets

[TobiasKadelka]

The normal use-case of onyo new -t is to give it the name of a template in the dir .onyo/templates/.

On the other hand, onyo new -t does error if used on a "normal" asset in the inventory, e.g.:

❱ onyo new -t groups/<path to asset> -d groups/<user> --edit
ERROR: Template groups/<path to asset> does not exist.

However, it is possible to use onyo new -t <yaml outside of onyo>:
onyo new -t ~/<path to asset> -d groups/<user> --edit

This leads to the awkward situation, that I can use onyo new -t on any type of asset, but only if I before copy it to a location outside of the inventory. I think this is weird, and onyo new -t should allow to get a normal asset and use this as the template (like onyo new --clone already allows, too).

[aqw]

As part of Ben's work, the new behavior will be:

• --yaml accepts YAML a yaml file from anywhere, and allows pseudokeys to behave as "instructions"
• --template is the same as --yaml, except it will also auto-serialize directories (i.e. call onyo show internally)
• --clone will autoserialize directories/assets (i.e. onyo show internally).