refactor(API): Distinguish between different types of helpers

Divide the helper methods into three groups:

1. Internal functions that are specific to the API class but do not
require access to self. These go in "api_helpers".

2. Functions that are used for the API class but may also be useful
to higher-level or custom web frameworks building on Falcon. There
are presently two such functions, both related to routing, so they
go into a new module, "routing". These functions will be included
in Falcon's reference documentation, and care must be taken to
avoid introducing breaking changes to them in future versions of
the framework.

3. Functions that only need access to self for performance reasons,
which would otherwise reside in "api_helpers". These go inside the
definition of the API class itself.
Fix broken link in README.md

Link to marconi WSGI is now zaqar wsgi
Merge pull request #372 from kgriffs/routing

refactor(API): Distinguish between different types of helpers
Merge pull request #373 from lwcolton/patch-1

Fix Broken Link in README.md
doc(README): Add note about mailing list

Add some information to the README about the Falcon mailing list,
including how to subscribe and a short note about expected conduct.
chore: Bump version to 0.2.0b1
docs(API): fix the mess-up in the nested middleware
fix(Request): Improve HTTP_RANGE support

 - Add a test to check whether "bytes=" is supported
 - add a simple way to support the "bytes=" prefix by stripping it if present
This should not break backward compatibility.

Fix #380
Merge pull request #379 from jeffrey4l/wrong_doc

Fix the wrong doc in the falcon.API
Merge pull request #382 from Joacchim/master

Improve HTTP_RANGE support, Fix #380