Adding a FAQ entry for connecting to tor's control port directly

Adding the "Can I interact with Tor's controller interface directly?" FAQ
entry. This covers how to connect to tor's control port/socket in each
scenario. This was inspired by Jen's StackExchange answer on...

  https://tor.stackexchange.com/questions/1449/authenticate-telnet-connection
Capitalizing proper nouns

I'm horribly inconsistent about this. Capitalizing 'Stem', 'Tor', and 'Python'.
Probably missed a few.
Using sub-headers for connection/authentication methods

Using headers rather than an unordered list for the sections so we can link
directly to them.
Controller sometimes provides microdescriptor router status entries

As pointed out by mr-4 on...

  https://trac.torproject.org/7646

Tor's 'GETINFO ns/*' methods provide standard v3 router status entries when Tor
isn't using microdescriptors, and microdescriptor flavored entries when it is.
Changing our Controller's get_netword_status() and get_network_statuses()
methods to provide the right return type.

This is a clunkier for our users but there's not much that Stem can do about
that. Oh well. :(
Minor tutorial revisions

Took a quick read through our tutorials. Just minor reordering and rewording.
Improving our FAQ and making entries more succinct

Reordering and rewording our FAQ. This moves examples for the 'How do I connect
to Tor?' examples to their respective modules to both make the FAQ entry more
readable, and the modules more informative.

This also dropped the "How do I get information about my exits?" FAQ entry
since it's largely redundant with the 'Determine The Exit You’re Using' example
in our tutorials.
Adding a 'Scripts' section to our examples page

Coderman suggested a cookbook section on #tor-dev. I like this idea. On
occasion I write one-off scripts for specific tasks. These would make fantastic
examples for new Stem users, so starting a section on our examples page for
them.

I recall writing another script for 'list the contact information of all
outdated relays' for a ticket. I'll dig that up later and add it.
Moving "Determine The Exit You’re Using" to the example scripts

Moving this example from our client usage tutorials to the example scripts.
This is a good standalone example, and unrelated to the other tasks in the
tutorial.
Adding example for listing outdated relays

Adding our script from ticket 9476 which prints contact information for relays
prior to a given version. I picked example output that was especially obscured
addresses, then modified them further to make them useless to scrapers. ;)
Making CircuitEvent sortable

Circuits should be sortable by their id. Making that the case so the following
works...

  for circ in sorted(controller.get_circuits()):
    ... do stuff...
Adding an example for listing circuit information

This is an adapted from of the 'How do I get information about my exits?' FAQ
entry I recently removed. Unlike that example, this provides information about
the full circuit rather than just the last hop.
Improving syntax highlighting

Took a peek and Sphinx's docs for syntax highlighting, and using a bit of it...

* Using the lighttpd lexer for torrcs since it both fades comments and
  emphasizes torrc keywords. This is a hack, and doesn't work if torrc entries
  have a ':', in which case I'm using a bash lexer instead.

* Highlighting part related to event handling for its tutorial.

* Specifying python highlighting for a couple python snippet in the faq.
Adding munin-tor to our examples

Neat plugin from Martin for Munin...

  https://lists.torproject.org/pipermail/tor-relays/2014-March/004168.html
Adding exit-funding to our examples

Adding Moritz's script to determine how much funding exit operators should get.
Back buttons for tutorials and example scripts

Adding a '<< Back' button to our tutorials and example scripts to make the
pages easier to navigate. Most pages on our site are a pretty flat hierarchy
(download, faq, etc), but these are an exception to that so it's handy to be
able to go up a level.
Moving ExitMap to the applications

We listed ExitMap a while back, but I just realized Philipp made a really nice
site for his Spoiled Onions paper...

  http://www.cs.kau.se/philwint/spoiled_onions/

Linking to that rather than his GitHub repository, and moving this up to the
section reserved for sizable applications.
Dropping back button from top level tutorials

On reflection the nav bar already links to the top level tutorial page so
there's no need for a back button for that. I *am*, however, keeping the button
on the example scripts since it's useful there.
Merge branch 'master' of git://gitweb.torproject.org/stem