Fix #811

Turns out that resetCollections was setting docpad.generated to false.
But our docpad.generated = true assignment would only fire if
opts.initial was true. However, that would not be true if we are a
non-initial reset generation.

I’ve moved the reset task to be the first, and moved the opts
assignment after it. So that opts can be assigned based on their
correct values which can be determined after the reset tasks fires or
doesn’t fire.

I’ve also added a check for this invalid state in case it ever occurs
again.
Detection for #792

We need to catch this error somehow.

As it seems this error is suppressed due its location, let’s make it
way more prevalent so we can get this resolved.
Fixed #801

Went with the simplest option of implementation which is only changing
it for the charset.
v6.63.7. Bugfix.

- v6.63.7 February 21, 2014
	- Fixed IE9 and below not understanding the charset we send
		- Thanks to [Eric Vantillard](https://github.com/evantill) for [issue #801](https://github.com/bevry/docpad/pull/801)
	- Better debugging for invalid watch states
		- For more information see [issue #792](https://github.com/bevry/docpad/issues/792)
	- Fixed DocPad failing to serve files after the initial generation once the docpad configuration file has been modified
		- Thanks to [Michael Williams](https://github.com/ahdinosaur) for [issue #811](https://github.com/bevry/docpad/issues/811)
	- Updated dependencies