feat(csi): add CSI manifests

[Al-Pragliola]

Description

Added manifests for CSI deployment, the following:

    - name: MODEL_REGISTRY_BASE_URL
      value: "model-registry-service.kubeflow.svc.cluster.local:8080"

cannot be parameterized as an env from configmap because the way kserve works is to use it as a template for an initcontainer that is injected into the serving deployment, so it has to be viewed as a fallback URL to reach the default model registry.

How Has This Been Tested?

docker build . -f Dockerfile -t mr/mr:0.1.1
LOCAL=1 IMG=mr/mr:0.1.1 ./scripts/deploy_on_kind.sh

then followed the guide from csi/GET_STARTED.md

Merge criteria:

• All the commits have been signed-off (To pass the DCO check)

• The commits have meaningful messages; the author will squash them after approval or in case of manual merges will ask to merge with squash.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work.
• Code changes follow the kubeflow contribution guidelines.

[tarilabs]

it has to be viewed as a fallback URL to reach the default model registry.

/lgtm

cc @lampajr

[lampajr]

Thanks @Al-Pragliola! 🚀

/lgtm
/approve

[tarilabs]

Note for release strategy #435
for pinning the version in the manifest while releasing

pushd manifests/kustomize/options/csi && kustomize edit set image kubeflow/model-registry-storage-initializer=kubeflow/model-registry-storage-initializer:v0.2.9 && popd

ref also https://github.com/opendatahub-io/model-registry/wiki/Notes-on-Releasing-Upstream,-Midstream-model%E2%80%90registry/_compare/7c4b82724a1d66a0113589bd45ed9c25e57412eb

---

thanks a lot for the contribution @Al-Pragliola 🚀 next step: sync KF/manifests, so eventually also this can be referenced from the next MR release synced!

/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lampajr, tarilabs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tarilabs]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment