[charts] Ensure reduce motion preference disables animation on page load

[JCQuintas]

Fixes #13477

Could be a starting point for #13964

• Created a AnimationProvider which currently only holds the skipAnimation value
  • Migrated away from the useReduceMotion hook, as it got merged into the provider above
  • An alternative would have been to run the hook on every component that previously accepted skipAnimation, but that felt unnecessary, and the chosen solution could path a way to customising animations

By moving it to the provider, and passing it as a prop to all animations, we ensure immediate is called with the correct prop. I've left Globals.assign in place just in case, but it shouldn't be necessary anymore.

Testing

Emulating reduced motion in chrome

https://developer.chrome.com/docs/devtools/rendering/emulate-css#emulate_css_media_feature_prefers-reduced-motion

Running locally

pnpm --filter docs build && pnpm --filter docs serve

[mui-bot]

Deploy preview: https://deploy-preview-14417--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 9637c1c

[codspeed-hq]

CodSpeed Performance Report

Merging #14417 will not alter performance

_{Comparing JCQuintas:skip-animation-on-page-load (9637c1c) with master (c2cff49)}

Summary

✅ 3 untouched benchmarks

[JCQuintas]

Failing tests are unrelated #14457

[alexfauquette]

Not a big fan of @default undefined because all props are by default undefined

May be more interesting to describe what happends by default

If unset, charts addapt the user's prefers-reduced-motion preferences

By the way since false does not allow to overrid the user preferences (which I think is expected) why not setting false as the default value?

[JCQuintas]

Adjusted it to:

If unset or false, the animations respects the user's prefers-reduced-motion setting.

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.