Explicitly require forwardable

Was relying on coincidental require
Move all_files to support (and fix yield order)

We already have a support library, so things like `all_files` should be
there (since it's not only relevant to the base Bumbleworks module..
further refactoring forthcoming).  Also, fixed the yield order - since
the method is aggregating files from a directory, the expected result is
pathnames (which a Dir glob would give us).. the name is extra candy.
This also enables us to only use the first param in block params if we
just need the path.
Friendlier .configure; pre-refactor consolidation

Bumbleworks.configure now allows for multiple configuration blocks.
To ensure you're starting with a clean configuration, you can either
.reset! first, or use the new .configure! method, which clears config
but isn't as brutal as .reset! (doesn't reset other instance vars or
purge the dashboard).  Also starting to pull helpers into main singleton
to prepare for refactoring; we need better consolidation of concerns,
before the Bumbleworks singleton becomes a monolithic beast with
infinite power and no clear purpose.  Let's be honest, and not "extract"
methods into helpers that we just end up including anyway. :)
Task also extends forwardable; fix require order

Require forwardable before task, so task can extend as well
Upgrade some gems