Update dependencies and (mostly) clear npm audit

[gorner]

• ran ember-cli-update to update ember-cli addon blueprint to 3.3 3.4, and updated acceptance tests to work with current test APIs
• cleared most npm audit issues; resolves hoek security issue (downstream dependency) #187 (but excluding one minor issue dependent on pending ember-try 1.0 release)

[jbailey4]

@gorner Looks good, could you rebase and fix the couple merge conflicts.

[gorner]

@jbailey4 Done.

[blkeller]

While you're in here, is there any chance you would be able to bump the 'broccoli-funnel' dependency to 2.0.1 (the latest)? npm is still throwing a deprecation warning for 'exists-sync', which 'broccoli-funnel' depended on until version 2.0.1.

According to their changelog, it looks like the reason for the major version bump was simply because they dropped support for node 0.12. Meanwhile, this PR already declares node 6.x as the minimum supported version for 'ember-cli-sass'.

[jrjohnson]

Friendly bump. Would love to see this merged as it will remove a few distracting build warnings from our app now that broccoli-funnel is updated here.

[BryanCrotaz]

bump - this is the last addon we use that requires babel 5.x

[gorner]

@aexmachina if there's any other assistance you need from my end for this, please let me know!

[simonexmachina]

Nice, thanks for this - and thanks for the reminder.

[simonexmachina]

I assume that this would be a patch-level version bump?

[gorner]

@aexmachina The change in acceptable node versions (package.json line 61) might be interpreted as a breaking change, though Node 4.x has been already end-of-life since this past April. Otherwise I don't see anything that would qualify as an enhancement or breaking change.

Edit: on second thought, perhaps the updated (prod) dependencies would suggest an enhancement-level bump?

[jrjohnson]

I have seen other addons mark a major version when dropping node 4.

[simonexmachina]

Okay good point. I've published v9.0.1