Use named import of 'history' module to fix #5576.

[RoboBurned]

Fixes #5576
The issue is when we have something like
import createBrowserHistory from 'history/createBrowserHistory'
you get file included into the result dist:
node_modules/history/createBrowserHistory.js
And then when you import something like
import {smth} from 'history'
and your webpack or other build tool is configured to read packages.json>module property then it includes node_modules/history/es/index.js and then node_modules/history/es/createBrowserHistory.js
So both files are included:

node_modules/history/createBrowserHistory.js
node_modules/history/es/createBrowserHistory.js

[pshrmn]

This looks fine to me.

@RoboBurned I assume that you have built a project with these changes and it only included the history code you expected it to, yes?

This will also break cherry picking (I assume that is why this was written this way), but I'm not sure if we are still supporting that anyways.

[timdorr]

Sorry, forgot to mention this, but the import brackets should have spaces on the inside for consistence. E.g.:

import { createBrowserHistory as createHistory } from 'history'

[RoboBurned]

@pshrmn, yes, after these changes project includes only one copy of code from history/es directory.
@timdorr, I've added missing spaces.

[timdorr]

Thanks!