Change from grafonnet-lib to grafonnet

[NissesSenap]

Is your feature request related to a problem? Please describe.
grafonnet-lib has been archived, and we should go over to grafonnet instead.

Describe the solution you'd like
Ether that we support both grafonnet-lib and grafonnet for some time. But depending if grafonnet is backwards compatible or not, it would be nice to just change over to the new vrsion.

Describe alternatives you've considered
N/A

Additional context

#1279

[NissesSenap]

@olejeglejeg do you have any thoughts on this.
Have you any input on this one? What would be the impact of changing over to grafonnet from grafonnet-lib?

[olejeglejeg]

Hi @NissesSenap

It will be breaking change because libs have different contracts and it might significantly affect customers after upgrade.

It's not a smooth way, but currently, you can suggest clients provide new lib as a runtime build input, example here. Or operator needs to provide functionality to delegate managing libs set to the team that owns it, but it makes the operator logic of resources sync more complex.

P.S. The deprecation of grafionnet-lib was one of the factors why we suggested runtime builds since we use new version.