Support Input validation for Kubevela Application manifests

[bugbounce]

Describe the bug

Currently Kubevela doesn't seem to have a mechanism to validate input fields in an Application before applying the manifest. Currently, the Application manifest deployment fails with an error with the workload output. This makes it difficult to debug, especially for end users.

To Reproduce

Steps to reproduce the behavior:

1. Install Kubevela and Crossplane with Upbound AWS DynamoDB provider enabled.
2. Install the following Component Definition

apiVersion: core.oam.dev/v1beta1
kind: ComponentDefinition
metadata:
  name: dynamodb-v0
  namespace: vela-system
spec:
  schematic:
    cue:
      template:
        "output: {\n\tapiVersion: \"dynamodb.aws.upbound.io/v1beta1\"\n\tkind:       \"Table\"\n\tmetadata:
        name: \"tenant-\" + parameter.governance.tenantName + \"-\" + parameter.name\n\tspec:
        {\n\t\tname:   \"tenant-\" + parameter.governance.tenantName + \"-\" + parameter.name\n\t\tregion:
        parameter.region\n\t}\n}\n\nparameter: {\n\t// +usage=Name of the DynamoDB
        Table. Tenant prefix will be added automatically.\n\tname: string\n\t// +usage=AWS
        region where the DynamoDB Table will be created.\n\tregion: string\n\t// +usage=Attribute
        definitions, only required for hashKey and rangeKey attributes.\n\t// +usage=Governance
        metadata used for attribution of resources in Kubernetes and AWS.\n\tgovernance:
        {\n\t\t// +usage=Tenant name. Will be prefixed to the requested name of the
        Table.\n\t\ttenantName: string\n\t}\n}\n"
  workload:
    definition:
      apiVersion: dynamodb.aws.upbound.io/v1beta1
      kind: Table

3. Install the following Kubevela Application with properties.name missing.

apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: test-kubevela-dynamodb-required
spec:
  components:
    - name: myapptable
      type: dynamodb-v0
      properties:
        region: us-west-2
        governance:
          tenantName: test

4. Error:
   run step(provider=oam,do=component-apply): GenerateComponentManifest: evaluate base template component=myapptable app=test-kubevela-dynamodb-required: failed to have the workload/trait unstructured: output.metadata.name: non-concrete value string in operand to + (and 1 more errors)

Expected behavior
We expect a relevant error from the point of view of the end user defining the Application. The current form of the error cannot be interpreted by the end user. Kubevela should validate the Application manifest before applying and return any errors.

KubeVela Version

Vela Core : 1.9.10

Cluster information

• Kubernetes Version v1.28.8+k3s1

Additional context

• Cue lang has gained support for identifying missing fields since version 0.6.0. https://github.com/cue-lang/cue/releases/tag/v0.6.0
• We could also use something like [Feature] Create a ApplicationTemplate CRD for allowing Kubevela to template the Application object itself #3869
• This could be implemented in the appfile parser https://github.com/kubevela/kubevela/blob/master/pkg/appfile/parser.go