Allow traits to identify its side effect which allows OAM runtime to optimize

[ryanzhang-oss]

The trait system is an important part of OAM. The OAM community has given us feedbacks and one common concern is that applying a Trait may cause the containers in the workload to restart. This is not a desired behavior in many production environments.

We propose to add a trait's side effect to our traitDefinition. This allows our OAM platform to optimize our trait behavior so that we can minimize the negative impact on the workload.

We will follow up with a design proposal

[wonderflow]

This issue should be related with patch trait , any trait which will affect pod should trigger version(upgrade)

[wonderflow]

I think we need strict mechanism to limit all patch trait can only affect workload by oam-runtime patch trait mechanism.