Is your feature request related to a problem? Please describe.
<MotionConfig> is great. However, some configuration options are exposed via a separate MotionGlobalConfig. One of the most important is skipAnimations, which is needed for environments such as e2e tests/visual regression testing.
Describe the solution you'd like
Could we move all configuration, or at least skipAnimations to MotionConfig? I realise non-react config is still needed, so maybe these interfaces could just mirror each other? Anything you can set in one, you can also set in the other.