feat(replacements): framer-motion to motion

[yutakobayashidev]

Changes

Created a replacement rule for framer-motion with its continuation package motion.

Context

The package has been published as motion since version 11.11.12 following the merger between Framer Motion and Motion One.

Proof:

• Package documentation: https://www.npmjs.com/package/motion
• Official announcement: https://motion.dev/blog/framer-motion-is-now-independent-introducing-motion

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[CLAassistant]

All committers have signed the CLA.

[rarkins]

This is not ideal because it could result in a rollback of versions.

I think that while @mattgperry is releasing both packages in parallel, maybe Renovate shouldn't proactively replace framer-motion with motion. If/once framer-motion is stopped then we no longer have a moving target for the replacement