Remove common invalid properties when updating kube resources

[richard-cox]

Epic #9016

• This is the first step to tackle the epic
• We should identify the common kube properties that are provided in existing resources that aren't needed when we update them
  • At the moment these are seen as console warnings (dev) or debug (prod) when updating them
  • As a starting, and possibly ending point, see shell/utils/create-yaml.js NEVER_ADD
• Once we know the common properties we should remove them when resources are saved
  • there's already some kind of concept of doing this for cleaning yaml (which uses NEVER_ADD)
  • we probably need to wire it in to the steve model save

[richard-cox]

Note - most of the common properties will be handled by the backend - see rancher/rancher#41772

[cnotv]

We need an unit test for this one, so we know what the utility is supposed to do...

[Shavindra]

Awaiting more clarification rancher/rancher#41772 (comment)

[richard-cox]

I added a comment that side, but in summary they should be removed

[cnotv]

@richard-cox we should stop mixing up configuration and utilities, so it would be nice to take this out and avoid confusion next time (or in a separated issue).

[izaac]

The release target fix was Rancher 2.7.7 where the fix validation execution was done.

I did the same repro steps to validate there wasn't a regression on Rancher v2.9.0-rc2
Steps detailed here.