Workload create/apply using a workload yaml file lacks validation to prevent inclusion of multiple source types

[shaheerkootteeri]

Please fill out the issue checklist below and provide ALL the requested information.

• I reviewed open and closed Github issues that may be related to my problem.
• I am reporting a bug that others will be able to reproduce.

Describe the bug

A clear and concise description of what the bug is.
We are able to create a workload using workload yaml with multiple sources. For example the below workload yaml file will successfully create but with source as source.image as subpath

apiVersion: carto.run/v1alpha1
kind: Workload
metadata:
  name: tanzu-java-web-app
  labels:
    apps.tanzu.vmware.com/workload-type: web
    app.kubernetes.io/part-of: tanzu-java-web-app
    apps.tanzu.vmware.com/has-tests: "true"
spec:
  params:
    - name: annotations
      value:
        autoscaling.knative.dev/minScale: "2"
  image: my-image
  source:
    subpath: my-path
    git:
      url: https://github.com/sample-accelerators/tanzu-java-web-app
      ref:
        branch: main
    image: my-source-image

🔎 Create workload:
      1 + |---
      2 + |apiVersion: carto.run/v1alpha1
      3 + |kind: Workload
      4 + |metadata:
      5 + |  labels:
      6 + |    app.kubernetes.io/part-of: tanzu-java-web-app
      7 + |    apps.tanzu.vmware.com/has-tests: "true"
      8 + |    apps.tanzu.vmware.com/workload-type: web
      9 + |  name: tanzu-java-web-app
     10 + |  namespace: default
     11 + |spec:
     12 + |  params:
     13 + |  - name: annotations
     14 + |    value:
     15 + |      autoscaling.knative.dev/minScale: "2"
     16 + |  source:
     17 + |    image: my-source-image
     18 + |    subPath: my-path
👍 Created workload "tanzu-java-web-app"

Upon updating the workload with same yaml file with --update-strategy=replace the apps cli errors with message as Error: [--git-*, --source-image]: Required value: expected exactly one, got both

tanzu apps workload apply -f workload.yaml  -y --update-strategy=replace

I was also able to create/ update a workload with both maven in spec.Params as well as spec.image on workload yaml

Expected behavior

A clear and concise description of what you expected to happen.
Should't it behave the same way for creation as well as update? Also should we error usage of multiple sources while creating a workload using yaml file?

Steps to Reproduce

Steps to reproduce the behavior:

1. create a workload yaml using above
2. apply workload yaml using command

tanzu apps workload apply -f PATH_TO_workload.yaml  -y 

3. see the output
4. run the below command and see the error output.

tanzu apps workload apply -f PATH_TO_workload.yaml -y --update-strategy=replace 

Screenshots

If applicable, add screenshots to help explain your problem.

Version (Apps plugin version, Version of K8s running on cluster)

Put the output of the following commad

tanzu version && tanzu apps version

version: v0.28.1
buildDate: 2023-03-07
sha: 0e6704777-dirty
v0.12.0-build.2-dev-9344335a

### Environment where the bug was observed (cloud, OS, etc)

### Additional context & Relevant Debug Output (Logs, etc)
Add any other context about the problem here.

[heyjcollins]

We will not be executing this because update has been removed from the plugin