Add new debugtoolbar. settings for configuration

Since pyramid_debugtoolbar is a stand-alone application from the view
point of Pyramid, it does not inherit any of the settings from the
application it was started from. This means that things like
pyramid.reload_templates and pyramid.debug_notfound are not brought over
from the end-users application.

In most cases this is desirable, it becomes problematic when the user is
attempting to create a debugtoolbar panel and is constantly modifying
the templates.

This changes introduces a bunch of new configuration variables that may
be set, they are outside the scope of the standard Pyramid configuration
and are namespaced to the debugtoolbar. This allows one for instance to
turn on the reload_templates feature in the debugtoolbar, while keeping
it turned off in the end-users application.
Add documentation for new configuration variables
Update tests to be aware of new configuration knobs
Update CHANGES.txt
Sign CONTRIBUTORS
\n
Add debugtoolbar template_reloading to demo
Remove debug_templates, it is a no-op
Merge pull request #159 from bertjwregeer/fix.template_reloading

Fix: template reloading
- Grammar and formatting corrections, and removal of reference to injection of overlapping/obscuring HTML by dbt now that it is in a separate window.
Merge pull request #160 from stevepiercy/master

- Grammar and formatting corrections, and removal of reference to inject...
- remove stray '
Merge pull request #161 from stevepiercy/master

- remove stray '
docs update on custom panel
docs updates , as per requests in PR 162
add docstrings for debugpanel
add the DebugPanel to the api docs
cleanup the api docs for DebugPanel
more docs updates
clarify request param to render functions