Replace old model-mesh manifests to new manifests

[Jooho]

Description

The old model mesh manifest was independent of the upstream model mesh, so when the upstream model mesh manifest changed, it was very difficult to update the opendatahub manifest to follow its history. So the new manifest uses the upstream manifest as much as possible via an overlay, with only minor changes.
Inside this folder, there are now two main component manifest folders: odh-model-controller, odh-modelmesh-controller
Each component utilized the manifest from the main repository as much as possible and used overlay or params.env for other components.

How Has This Been Tested?

The way how to use the model-mesh manifests is the same as before so you can test this with the kfdef that we used.

kind: KfDef
apiVersion: kfdef.apps.kubeflow.org/v1
metadata:
  name: opendatahub
  namespace: opendatahub
spec:
  applications:
    - kustomizeConfig:
        repoRef:
          name: manifests
          path: odh-common
      name: odh-common
    - kustomizeConfig:
        repoRef:
          name: manifests
          path: model-mesh
      name: model-mesh
  repos:
    - name: manifests
      uri: 'https://github.com/Jooho/odh-manifests/tarball/new-mm-manifests'

Merge criteria:

• The commits are squashed in a cohesive manner and have meaningful messages.
• 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

ISSUE: https://issues.redhat.com/browse/RHODS-8375

[anishasthana]

/retest

[Jooho]

/retest

[anishasthana]

/retest

[anishasthana]

/retest

[anishasthana]

/retest-required

[anishasthana]

/retest-required

[Jooho]

/retest

[Jooho]

@anishasthana Finally this passed all tests!. Could you please review this PR?

[danielezonca]

/lgtm

Well done :)

[anishasthana]

Approving as two component owners have approved/lgtm'd it.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anishasthana, danielezonca

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 [anishasthana]

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

[shalberd]

Follow-up minor issue relared to serving runtimes: https://github.com/opendatahub-io/odh-manifests/issues/809

Inconsistent usage of kustomization.images refs vs parameter (ovms).

[shalberd]

another error that came up previous to this master-level change, fixed with the changes in this PR / master:

svens-mbp-2:odh-manifests-1.6.1 s$ pwd
/Users/s/Downloads/odh-manifests-1.6.1

svens-mbp-2:odh-manifests-1.6.1 s$ kustomize version

{Version:kustomize/v4.5.6 GitCommit:29ca6935bde25565795e1b4e13ca211c4aa56417 BuildDate:2022-07-29T20:42:23Z GoOs:darwin GoArch:amd64}

svens-mbp-2:odh-manifests-1.6.1 s$ kustomize build  ./model-mesh/base
Error: accumulating resources: accumulation err='accumulating resources from '../dependencies/quickstart.yaml': security; file '/Users/s/Downloads/odh-manifests-1.6.1/model-mesh/dependencies/quickstart.yaml' is not in or below '/Users/s/Downloads/odh-manifests-1.6.1/model-mesh/base'': must build at directory: '/Users/s/Downloads/odh-manifests-1.6.1/model-mesh/dependencies/quickstart.yaml': file is not directory

[bdattoma]

with the odh-model-controller overlay. should this text be removed since the overlay got removed? @Jooho

[Jooho]

Good Catcher. Right, this should be deleted.