Mechanism to disable motion on a per motion component instance

[pixel-perfectionist]

In order to adequately react to instance level changes we need a mechanism to disable motion per instance, in addition to the global setting provided by Teams, browser, or OS.

[layershifter]

Let's avoid adding new mechanisms. There is already MotionBehaviorProvider & null can be passed to motion slots.

[ling1726]

@akatrukhin can you please add more details to your PoC PR to show how components would be affected by this change?

[robertpenner]

Discussed this with @akatrukhin, taking into account the feedback from Shift and Ling. We agreed:

• This isn't necessary for beta.
• The solution for resolving the conflict between 2 levels of MotionBehaviourContext in Teams is different than this feature, and seems to be best handled with a simple boolean expression in Teams code.
• There may use cases for this feature in the future, but it's not a priority, and as @layershifter said, we want to keep the mechanisms simple at this stage.
  Thus, we are closing this ticket.