Add valuesBlock and defaultValuesBlock and their conversion

[SimonTheLeg]

What this PR does / why we need it:

This PR adds makes the new fields valuesBlock and defaultValuesBlock of AppInstalls and AppDefs available in the api. In addition on POST & PUT requests for AppInstalls/AppDefs the values/defaultValues fields are being converted to their valuesBlock/defaultValuesBlock equivalent.

Which issue(s) this PR fixes:

Fixes kubermatic/kubermatic#12941

What type of PR is this?

/kind feature

Special notes for your reviewer:

Does this PR introduce a user-facing change? Then add your Release Note here:

valuesBlock and defaultValuesBlock fields are now available via the api

Documentation:

NONE

[Waseem826]

Do we still need any UI changes after this?

[SimonTheLeg]

I am not 100% sure. If the UI can also handle a ValuesBlock response from the BE then I think we are already fine.

In case we need to touch the FE code: I would appreciate if we could make all PUT/POST requests also use the new valuesBlock field (but only if it is not too much work).

[Waseem826]

/approve

[kubermatic-bot]

LGTM label has been added.

Git tree hash: 874889ffe9c43a174c889fa2bd9875aa29ea8974

[Waseem826]

/cc @ahmedwaleedmalik

[ahmedwaleedmalik]

/approve

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahmedwaleedmalik, Waseem826

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:

• modules/api/OWNERS [ahmedwaleedmalik]
• modules/api/pkg/OWNERS [ahmedwaleedmalik]
• modules/api/pkg/api/OWNERS [ahmedwaleedmalik]
• modules/api/pkg/handler/OWNERS [ahmedwaleedmalik]

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

[Waseem826]

It seems like the API still uses values for applications added during cluster creation. It uses valuesBlock only for the applicationinstallation endpoint.
I added an application during cluster creation and the application installation returned values field (no valuesBlock field in response).
If I add/update an application installation later on (from cluster details page), API returns the new valuesBlock field.

[SimonTheLeg]

oh I see. This is something I did not consider. I'll have a look at it and will write a fix.