Make the value in the resource configuration source an apiextension JSON object instead of string

[Skarlso]

What would you like to be added:

We have this:

type ConfigurationRuleYAMLSubsitutionSource struct {
	// Value is the value that will be used to replace the target in the file.
	Value string `json:"value"`
}

Should be something like this:

type ConfigurationRuleYAMLSubsitutionSource struct {
	// Value is the value that will be used to replace the target in the file.
	Value *apiextensions.JSON `json:"value"`
}

To allow for arbitrary json values.

Why is this needed:

[jakobmoellerdev]

I believe the yaml substitution engine is not powerful enough yet to handle structure replacement of fields. We will have to think about how we go with this. Also, since the localization is not technically part of the OCM lib, we should probably move the entire logic out into the controllers as another task. WDYT?

[Skarlso]

I'm fine with moving it, but this is isn't working right now, and I don't have another option of just plain exchanging a number.

The value being json probably isn't working, but then we'll have to rethink how we do the substitution. Because right now, only strings are working. :)

[jakobmoellerdev]

lets split this into 2. parts:

1. allowing numbers (that one we can support simply with the change you suggested)
2. allowing arbitrarily nested structs (that requires the lib change

WDYT?

[Skarlso]

Sounds good to me 👍