Cleanup of caikit OOTB

[lucferbux]

Description

Closes #2143

How Has This Been Tested?

1. Deploy the new template with oc apply -k manifests/modelserving
2. Create a new Caikit deployment with kserve
3. Check that you can infer the results

Test Impact

No testing involved

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

[lucferbux]

@andrewballantyne @Xaenalt This is the cleanup PR for caikit. The renaming of the file is not needed, since it's an internal file and there's no implication whatsoever to the final product. I can do it if you want but I don't see the need.

[bdattoma]

maybe we could add the version metadata as well, otherwise user will see this in the UI:

@Xaenalt does the runtime have a specific version?

I would say we could review the need of (name - version) in the UI since the metadata is not mandatory.

[lucferbux]

/lgtm

[openshift-ci]

@lucferbux: you cannot LGTM your own PR.

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[lucferbux]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lucferbux

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

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

[lucferbux]

maybe we could add the version metadata as well, otherwise user will see this in the UI:

@Xaenalt does the runtime have a specific version?

I would say we could review the need of (name - version) in the UI since the metadata is not mandatory.

We can add that as a follow up!

[bdattoma]

@lucferbux follow up issue: #2189