Fix syncAlways option use in blocksSaga

[mnaamani]

Solves #93

• Correctly pass syncAlways argument
• Iterate over drizzle.contracts object with Object.keys() instead of map
• Add all missing import from redux-saga/effects

[mnaamani]

@DiscRiskandBisque should we include the dist/drizzle.js and package-lock.json in the PR?
I'm assuming we shouldn't and that step will be done in a seperate PR by maintainers when merging into master and prior to publishing to npm?

[OnlyOneJMJQ]

@mnaamani Thank you for this! No need to include the build--you're correct that we'll run the build command before pushing to develop/master.

A little more background on this decision (it is a controversial one 🙂): In the interim before moving toward a more traditional release structure (akin to canary -> beta -> release -> lts) we're using the build folder as a quick nightly.