Handle defaults differently (aka do not change specs)

[nicolaferraro]

I'm working on upgrades and I think we have a issue with defaults.

We use the integrationplatform as global config location and if a property is not set on the platform, we set its default value in the spec during the "initialize" phase.

E.g. when initializing a empty integrationplatform we set runtimeVersion to 0.3.3

But if we upgrade Camel K to a version that uses runtimeVersion 1.0.0 by default, we can't tell if that 0.3.3 was set by the user or was a default value added by the previous release.

We should compute defaults without writing them into the spec field.

[lburgazzoli]

We can put them in the status and reset them on platform re-initialization ? having the default visible is quite useful (imho)

[nicolaferraro]

Yeah.. or I remember some tool that was writing the "applied configuration" in an annotation.. status is cleaner of course

[nicolaferraro]

Fixed by #1127