refactor(karma-webpack): Remove lodash from dependencies

[Chalarangelo]

This PR contains a:

• bugfix
• new feature
• code refactor
• test update
• typo fix
• metadata update

Motivation / Use-Case

In an attempt to remove dependencies that are barely used in popular npm packages, I have replaced lodash's clone method with an inline clone function with the same functionality. Based on that and provided that lodash is not used anywhere else in this package from what I can tell, the dependency on lodash has also been removed from package.json.

Breaking Changes

Additional Info

[jsf-clabot]

All committers have signed the CLA.

[ryanclark]

Thanks for your PR, removing lodash is great. I only see one issue - can you change your clone function to work on nested objects/arrays? The webpack config is nested so if we're doing a clone it should be deep.

Alternatively, we might not even need to clone it - I'm not sure why it is. If this is so, we can just remove both the clone part and lodash.

[matthieu-foucault]

• _.clone is a shallow clone, so no need to make the clone function recursive (if we need it at all).
• Given that Object.assign({}, undefined); and Object.assign({}, null); both return {}, there's no need for those || {}

[matthieu-foucault]

Should the updated package-lock.json be committed as well?

[ryanclark]

@matthieu-foucault thanks - I don't personally use lodash. I agree with your second point then I'm happy with it - also the package-lock.json does need to be committed.

[Chalarangelo]

• package-lock.json updated.
• Removed the || {}.

Anything else?

[matthieu-foucault]

Look good to me