feat: add create/update/delete commands for template

[BlueLabelscotch]

Summary

Rounds out the template noun with create/update/delete commands, which previously only supported list/get.

• create template — POST /template/api/templates
• update template — PUT /template/api/templates/update/{id}/{version}
• delete template — DELETE /template/api/templates/{id}/{version} (version is a required path segment; there's no bare "delete all versions" endpoint)
• multi_level: true on the template noun, so --level account|org|project works across all five template commands
• Added a yaml field on the noun (get template now shows the raw template YAML, matching how input_set already does this)
• Fixed an existing bug in list template: flags.list-type was being parsed as subtraction by the expression evaluator, so templateListType was silently dropped from every request; changed to flags["list-type"]

Testing

Manually tested against a live account:

• get template <id> --version <v> — confirmed yaml field renders
• delete template <id> --version <v> — confirmed request path (--debug) hits /templates/{id}/{version}, not the old query-param form
• list template --level account / --level org — confirmed scope is dropped correctly per level
• update template — request is well-formed and tested.

[sawka-harness]

Ah the versioning is really interesting here.

We should add a new noun "template_version". So we have "get template" (gets latest), but also "list template_version" and "get template_version" to get specific versions. I guess "create template" creates a whole new template, and "update template" mints a new version. So then we only have "delete template_version".