Document pants.ini configuration options.

Mostly a repost of https://rbcommons.com/s/twitter/r/67/ post move to
pantsbuild.

Add a simple system to register pants.ini options so we can generate a
configuration reference page on our website. Lots of required, undocumented
keys in pants.ini has been identified as an issue for new users and this
change lays the groundwork. Once the pattern has been defined I'll move all
options over to this style in a few future reviews.

Similar to command-line flags, pants developers explicitly define options
rather than fetching keys from the config directly. We register these keys
enabling the generation of a docs site. A few examples are provided here, and
we'll do the rest after reaching consensus on the format. The goal is
generating documentation for our users, so we explicitly avoid going overboard
and rewriting the whole config system (e.g.: unifying pants.ini & command-line
flags which is out of scope for this change).

Eliminate two options that are not obviosuly desiarable to allow users to
tweak. In 67 we agreed to remove these rather than document as tuneable:
tasks.build_invalidator, reporting.reports_dir

Reviewed at https://rbcommons.com/s/twitter/r/183/
Update RBTools to 0.6 (was 0.5.5).

Testing Done:
Posted this review with 0.6.

Reviewed at https://rbcommons.com/s/twitter/r/186/
doc: += Pants caches stuff. and if you don't know that, you do silly stuff
Fixup pants binary constraints.

Limit compatibility to 2.6 through 2.7 and 3.3+ to avoid issues
with 3.0 through 3.2 not supporting unicode literals.  This now
explicitly runs afoul of pants import headers.
Create README.md
Update README.md

Tweak the CI orb link to hit the branches view
docs: BUILD dictionary: fix method doc format; don't show fancy_pants
Merge branch 'master' into lahosken_readme

Conflicts:
	README.md