Need better docs on staging your own FxA webservice endpoint

[crankycoder]

This is a rework of #5.

The FxA android library already contains a demo client, but you need to have control of a FxA enabled web service with an endpoint that handles FxA redirects.

A sample endpoint is already included and it is the one which we use to test the FxA android library. We really need to get some documentation around this to show people how to stage their own endpoint.

Concretely - the endpoint is written with the Python Falcon API.

Docs should minimally include:

1. Get the falcon endpoint running on a publicly facing port of a webserver
2. Configure the FxA demo client to point to the appropriate OAuth2 and Profile server
3. Provision a FxA application in the dash board and copy the client id to both the client and server. Also copy the client secret to the falcon endpoint.
4. Startup server
5. Compile, install and run the FxA demo client
6. Monitor adb log output to verify that the OAuth Destroy task eventually runs. Each task is chained to a next task, so if the Destroy tasks runs successfully - all tasks have executed as expected.

That should be it. We can skip nginx/apache for the purposes of developers. They just need to see that all FxA tasks actually do something from their android device via adb log.