Updated content to conform to README best practices template

Before alterations, this content was the module author-determined
description of and instructions for use of the module.

As part of a joint Forge/Docs team effort to standardize formatting and
encourage quality module documentation, a best practices README
template was created via internal and external user testing. That
template was then applied to this module.

I pulled in content from the original README on GitHub and the Module
of the Week blog post. A table of contents was added for navigability,
standard headings were added (Overview, Module Description, Setup,
Usage, Implementation, etc.) to organize content, existent and
pulled-in content was moved under its appropriate heading and edited
for tone/flow/clarity, links to outside documentation were updated, and
basic formatting was done to adhere to template standards.
Fixed typos, rewording and typsetting per feedback

Updated spelling errors, typsetting issues and some wording suggestions
based on module author feedback
Merge pull request #89 from laurenrother/master

Updated content to conform to README best practices template
Added support for tablespaces
Tablespacing improvements
Update spec/README.md
Improved tablespace rspec test
Final commit for 2.0.1 release; update CHANGELOG and Modulefile
Merge pull request #100 from kbrezina/master

Support for tablespaces
WIP
WIP - adding support for an 'included' config file
RSpec tests were fixed to work properly with included postgresql_puppet_extras.conf
Improved test result matching for the advanced PGS configuration test.
typo fix in example
Merge pull request #104 from boinger/master

Minor typo fix in README
Added test of the included postgresql configuration file
Added info about the advanced configuration file
Merge pull request #105 from kbrezina/feature/master/adding-include-to-pg-conf

Support for included configuration file
Add unit tests and travis-ci support

This patch includes some very basic and initial unit testing using rspec-puppet
and for the case of facts, just normal rspec.

I've taken a very light approach here as rspec-puppet can be quite combinatorial
when one gets carried away. For now I've just added basic compile failure
detection effectively for classes and defined resources. As we continue to work
on the code and find regressions this work can be expanded.

For facts and functions I've also taken a basic approach for now.

One little thing I did change, was the strange string that the fact returns
when the default version is undefined. Instead of an error message I've just
returned the string 'unknown' which is more in line with other facts I've seen
in the wild, and to be quite honest 'unknown' is fairly self-explantory. Since
a fact isn't an error reporting message this seemed more appropriate, and looked
nicer in the rspec test.

As far as travis-ci support, I've added the same configuration that @jmmcune
came up with for stdlib which is pretty light and reasonable standard now we
propogated that to 4 or so other modules in the puppetlabs/ namespace. It should
work out of the box.

Signed-off-by: Ken Barber <ken@bob.sh>
Merge pull request #115 from kbarber/ticket/master/unit_tests

Add unit tests and travis-ci support