feat: add clone action to recipe

kind: Recipe
spec:
  tasks:
  - name:
    clone:
      # state will provide apiversion, kind to filter the gvk
      # name is mandatory
      state:
      generate: 
        name:
        namespace:
        nameReplicas: # these many names i.e. resources will get created
        namespaceReplicas: # these many namespaces will get created

kind: Recipe
spec:
  tasks:
  - name:
    cloneAll:
      apiVersion:
      kind:
      labelSelector: 
      generate:
        name:
        namespace:
        nameReplicas:
        namespaceReplicas:

kind: Recipe
spec:
  tasks:
  - name:
    bulkClone:
      resources:
      - apiVersion:
        kind:
      labelSelector: 
      generate:
        name:
        namespace:
        nameReplicas:
        namespaceReplicas:

No files, tests, or entry points are named. Start by locating the Recipe task and action definitions in the repository, then compare existing action behavior before deciding where clone, cloneAll, and bulkClone belong. The YAML sketches do not define validation, cloning semantics, or completion criteria, so those requirements need clarification before implementation.