enhance manifest work controller code to resolve field dangling issue in OCM environment

[SkrPaoWang]

Use case scenario:
If a user deploys a manifest work in the OCM environment and this manifest work contains a deployment A which has a replica field value equal to 5. However, this OCM environment also has a HPA controller that owns and manages the replica field for every deployment. The HPA controller will change deployment A's replica field to 3, but after that the work agent will change deployment A's replica field back to 5 since the work agent thinks he owns the replica field so he will make sure the replica field equals the desired value. It will start an infinity loop, the deployment A's replica field will change from 5 to 3, 3 to 5, 5 to 3, 3 to 5...

It's not what we wanted. What we want is Deploy a manifest work deployment, and give one specific field ownership to another player, (for example give the replica field ownership to hpa controller) and let another player change some specific field (for example hpa changes replica field), and the work agent will not change it back.

[qiujian16]

/kind feature