EKS-A CLI template auto-import feature's destination folder

**What happened**:

EKS-A CLI's template auto-import feature imports a template into the "_datacenter_/vm/Templates" folder by default. If the 'Templates' VM-folder does not exist, it fails the import.

Error message:
_Validation failed {“validation”: “vsphere Provider setup is valid”, “error”: “failed deploying template: error deploying template: govc: folder ‘/datacenter-name/vm/Templates’ not found\n”, “remediation”: “”}
Error: failed to create cluster: validations failed_

**What you expected to happen**:

CLI's template auto-import feature should create the missing directory in the default path it uses for the import.

**How to reproduce it (as minimally and precisely as possible)**:

Ensure no VM folder called 'Templates' of exists under datacenter. Run EKS-A CLI.

Start at the EKS-A CLI template auto-import flow and the vSphere provider setup that uses the default datacenter/vm/Templates path. Reproduce the failure with no Templates VM folder, then verify that the missing folder is created and the template import succeeds.

Written by the indexing model from the issue text.