Transfer/Create service-provider-ocm repository

[Skarlso]

Description

Currently, the service-provider-ocm repository lives under https://github.com/Skarlso/service-provider-ocm.

There is code there, but actually, not that much that makes things work. Maybe it's worth generating a new repository with the latest template all together and then cherry-pick the most relevant changes and code segments from this repo.

We might also just take this one, and I will transfer it under the open-component-model organization as is and go from there.

Also, to be debated if we might want to have this thing under our mono-repo instead as a separate repository.

We most likely want it separated, just because the monorepo deals with all things OCM and this is more akin to MCP instead of OCM.

Done Criteria

• The repo is created/transferred to open-component-model organization

[frewilhelm]

Also, to be debated if we might want to have this thing under our mono-repo instead as a separate repository.

Please move it to the mono-repository (in kubernetes/). Please make sure that the script will still work

[Skarlso]

Is this your preference or did you talk it over with the rest of the team? :D

[frewilhelm]

We discussed this (super) shortly in the planning yesterday. @jakobmoellerdev's recommendation was to put it in the monorepo. However, he acknowledged that this might be tricky because of some scripts that expect a standalone repository (not sure on this one though)

[Skarlso]

Alright, let's see then how that will go. :)

[Skarlso]

Actually, this might get a bit hardy because of the submodule that has to be initialized to be able to use the service provider. 🤔 I think it would be cleaner. Especially if people wanting to use / develop the provider have to checkout THE ENTIRE open-component-model repo. I think this should live alone.