feat: controller changes for Side Inputs support

[whynowy]

Be able to orchestrate a pipeline spec like following:

apiVersion: numaflow.numaproj.io/v1alpha1
kind: Pipeline
metadata:
  name: simple-pipeline
spec:
  sideInputs:
    - name: s1
      container:
        image: my-s1-image
      trigger:
        schedule: "@every 300s"
    - name: s2
      container:
        image: my-s2-image
      trigger:
        interval: "@every 300s"
  vertices:
    - name: in
      source:
        http: {}
    - name: my-udf
       sideInputs:
         - s1
         - s2
      udf:
        container:
          image: my-image
    - name: out
      sink:
        # A simple log printing sink
        log: {}
  edges:
    - from: in
      to: my-udf
    - from: my-udf
      to: out

For a pipeline like above, following new resources will be created:

• Side Inputs data store in JetStream.
• Two Side Input Manager Deployments for s1 and s2, each of them contains 1 init container to check if the store is ready, and 2 containers.
• A new init container on the my-udf vertex pod, which is supposed to load the data from data store.
• A sidecar container to watch the data store changes.

[vigith]

Should we keep either use SideInput or SideInputs, but not both. WDYT?

[KeranYang]

Are we setting SideInputs store name the same as pipeline name? Maybe it worth documenting the rationale behind.

[whynowy]

It's just a unique name in a namespace.

[KeranYang]

Shall we unit test it?

[whynowy]

We should.

[whynowy]

done.

[vigith]

• Please make the mount point readonly for UDF
• Prefix namespace name to KV bucket name

[whynowy]

• Please make the mount point readonly for UDF
• Prefix namespace name to KV bucket name

done