new(demo): respect prefersReducedMotion and leverage in happo

[williaster]

This PR adds the following logic discussed in #1030

📝 Documentation

• checks for the prefersReducedMotion media query in the /xychart, /axis, and /patterns demos, and uses animated or unanimated components accordingly (also removes animationTrajectory controls accordingly).

EDIT: even if prefersReducedMotion=true, users can still toggle animation on/off.

🏠 Internal

• sets prefersReducedMotion: true for happo tests, and removes the happo rendering timeouts that were previously needed for animations

Tested the happo examples locally, and tested gallery examples with / without prefersReducedMotion set on my OS.

@lencioni @kristw @hshoff

[coveralls]

Pull Request Test Coverage Report for Build 516451309

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 61.749%

---

Totals
Change from base Build 514010163:	0.0%
Covered Lines:	1786
Relevant Lines:	2753

---

💛 - Coveralls

[lencioni]

Love it!

[lencioni]

I think it might be nicer to always render these controls, and then just disable them and add a message explaining why so that people who visit this page with prefers reduced motion are still able to see how it can be used. It would be even better if there was a way for these people to override and enable the animations anyway if they want to see the demo with the animations without having to mess with their OS settings or whatever.

[williaster]

good call, I updated the examples to have an enable animation toggle with a default determined by prefersReducedMotion.

[coveralls]

Pull Request Test Coverage Report for Build 516451309

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 61.749%

---

Totals
Change from base Build 514010163:	0.0%
Covered Lines:	1786
Relevant Lines:	2753

---

💛 - Coveralls