fix(container): createScope return defaults to original container

[moltar]

Closes #178

[coveralls]

Coverage remained the same at 100.0% when pulling c0c7160 on moltar:master into 7625dd9 on jeffijoe:master.

[jeffijoe]

Looks good! Can I ask you to do a few small things in this PR as well?

• Remove yarn.lock, run npm install to switch to NPM. Yarn seems to have gone off the deep end.
• npm i -D rimraf to fix contributing docs errors #179
• Run npx npm-check --skip-unused -u to upgrade all packages to latest, run lint and cover (I expect prettier@2 will format all files, that's fine)

[moltar]

Seems like outside the scope of a PR.

Maybe we should do a separate PR?

[moltar]

And for updates, wouldn't it better to setup @renovatebot?

[jeffijoe]

I'm fine with it being the same PR, the update will go out as a single release anyway, I am just trying to cut down on needless bureaucratic work.

I haven't set up automated releases for Awilix because I've had some issues with it in the past, and I also don't want to release a new version every 12 hours because of package updates 🤣

However anytime there are actual changes that need to be released, I update the deps before doing so.