feat: macro can customize importModuleName

[agriffis]

If styled should come from a wrapper instead of directly from
styled-components, this enables users of the macro to customize the
import by configuring in packages.json:

"babelMacros": {
  "styledComponents": {
    "importModuleName": "my-styled-components"
  }
}

Previously similar functionality landed in
babel-plugin-styled-components so users of the plugin could use
a wrapper at that level, but it wasn't available to users of the macro.
This builds on that work by passing the customized module name through
to the plugin. Consequently we also update the dependency to ensure the
plugin supports topLevelImportPaths

See styled-components/babel-plugin-styled-components@325167b

Fixes styled-components/xstyled#44

[quantizor]

I'd prefer to continue using the >= notation so we don't have to update the library here if v2 comes out that doesn't contain incompatible changes with styled-components core

[agriffis]

np, will force push that change

[quantizor]

Code looks great to me! If you could make that one change and write up a short changelog entry, that would be much appreciated.

[agriffis]

@probablyup That should be all set now. I force-pushed twice because I hadn't run yarn the first time, so yarn.lock wasn't updated.

Would you mind cherry-picking this to legacy-v5? Or do you prefer another PR?

[quantizor]

@probablyup That should be all set now. I force-pushed twice because I hadn't run yarn the first time, so yarn.lock wasn't updated.

Would you mind cherry-picking this to legacy-v5? Or do you prefer another PR?

Another PR please

[agriffis]

Another PR please

See #3432, thanks!