IE11 support

[mattgperry]

Fixes #364

Some enterprise customers have a requirement to support IE11. With polyfills, everything in Motion is supportable with the exception of Proxy. Motion uses Proxy to generate motion components for all HTML, SVG, and hypothetical web component elements.

This PR adds a new function, createDomMotionComponent. This can be used to create DOM motion components manually.

import { createDomMotionComponent } from "framer-motion"

const motion = {
  div: createDomMotionComponent("div")
}

Note: This PR doesn't add polyfills. The linked issue will help you get up to speed with the required polyfills.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 1efd8ba:

Sandbox	Source
Framer Motion: Simple animation	Configuration
App Store UI using React and Framer Motion	Configuration
Framer Motion: Reorder animation	Configuration
Framer Motion: growing item positionTransition issue	Configuration
Framer Motion: Image lightbox	Configuration

[mattgperry]

This is a holdover from the previous approach but it also makes sense as this folder is transpiled, not TypeScript

[magicspon]

Beeeeeelting...