Fix #2361: allow multiline properties by correctly encoding them

[nicolaferraro]

Fix #2361

@squakez mind having a look?

Release Note

Multi-line properties can be used in KameletBindings

[squakez]

I cannot easily understand the meaning of the toPropertyEntry function. I'd suggest to include a set of unit test in run_test.go just for this private function with clear input/output expectation. It will improve the readability and future updates.

[squakez]

The function is repeated in another unit, I'd avoid to include repeated code.

[squakez]

I think we can instead provide that value variable as a input variable of the fuction instead of props. You only use props to extract this value AFAICS

[squakez]

Now I've seen you already did it this way in the other function in common.go. I'd suggest just using this one then.

[nicolaferraro]

Right about refactoring the toPropertyEntry function. The meaning is to encode a k/v pair into a property-file line that can be written directly into a .properties file. A config entry in the integration/kit/platform will contain an encoded line for each property, which usually means a line having k = v, but it sometimes needs encoding e.g. when the value spans over multiple lines. I let the library encode the entry.

[squakez]

It looks good, thanks!