Reference KCLInput in the Composition from in cluster.

### What problem are you facing?
In my compositions, I would like to be able to reference a KCLInput that is already applied in cluster instead of mounting a cm or referencing an external git/oci repo.

```yaml
kind: Composition
# ...
mode: Pipeline
pipeline:
- step: basic
functionRef:
name: function-kcl
input:
apiVersion: krm.kcl.dev/v1alpha1 # side note: this seems to be the wrong group/version now?
kind: KCLInput
sourceRef:
name: basic # something like this
```

The development feedback loop for these functions hurt... Maybe I don't have the proper dev flow figured out yet?

### How could this Function help solve your problem?
If i could reference my KCLInput CRD in my composition directly instead of inlining I would be able to better revise and develop these.

Thanks for your work!

Start with the Composition pipeline input and KCLInput sourceRef shown in the issue, and verify the current apiVersion and group for KCLInput. Determine how an already-applied KCLInput could be resolved by function-kcl; done means a Composition can reference it by name without mounting a ConfigMap or using an external Git or OCI source.

Written by the indexing model from the issue text.