Upgrade ModelMesh to v0.11

[heyselbi]

Goal 1: Upgrade ModelMesh serving in ODH and RHODS to upstream's v0.11
Goal 2: Resolve the clashing of ModelMesh and KServe CRDs --> if not resolved by Goal 1 automatically, a separate issue should follow up.

Subtasks

• Sync modelmesh repository(main branch) with upstream/main
• Sync modelmesh-runtime-adapter repository(main branch) with upstream/main
• Sync rest-proxy repository (main branch) with upstream/main
• Sync modelmesh-serving repository(main branch) #175
• Upgrade odh-model-controller to use kserve v0.11.0 #172
• Create a new release branch from updated main branch
• Sync kserve repository(master branch) #173
• Update odh-manifest (fast image)
  • update fast manifests based on main branch #181 odh-manifests update in modelmesh-serving (to be later copied over separately to the correct branch in odh-manifests)
• Create modelmesh-serving PR to test OpenShift CI
  • Updating ModelMesh to v0.11.0 (Step 1) openshift/release#43219
  • Updating ModelMesh to v0.11.0 (Step 2) openshift/release#43096
• [ ] Update Dockerfile.develop.ci/go.sum.develop/go.mod.develop repository for openshift-ci
• Update AutoMerger mapping for the created release branch

To do list from @VedantMahabaleshwarkar

• Controller gen manifests will be in odh/modelmesh-serving/config/
  • main manifests dir is odh/modelmesh-serving/opendatahub/odh-manifests. So copy generated manifests from prev step into this directory
  • verify quickstart scripts work with new manifests

[vaibhavjainwiz]

template : #122

[Jooho]

@vaibhavjainwiz @heyselbi @VedantMahabaleshwarkar we only have 1 week for this task and I hope that it should be finished by end of the Tuesday. Then we can test it with an amount of time.

[heyselbi]

FVT CI tests are failing. The pods are crashlooping, unsure why yet. I am missing access to openshift org - requested it today. Vedant is currently trying to look into it without access to the CI cluster.

[heyselbi]

Update from JooHo:

• modelmesh serving images were built for fast/stable(v0.11.0)
• modelmesh/modelmesh-runtime-adapter/rest-proxy failed fvt because it used a wrong modelmesh-serving-develop (This openshift ci pr will solve this issue)
• I expect other images will be done by 1pm today.

[heyselbi]

All related PRs are attached. The ones that couldn't be attached:
opendatahub-io/odh-manifests#939
openshift/release#43384
openshift/release#43385
openshift/release#43426
openshift/release#43449
openshift/release#43460

[heyselbi]

Follow up: transition to RHODS: #228