Remove leading/trailing single or double quotes when parsing the my.cnf
file in mysql_user and mysql_db.

Do this so that these modules parse the my.cnf file the same way that
the mysql client does.

From: http://dev.mysql.com/doc/refman/5.0/en/option-files.html

    You can optionally enclose the value within single quotation marks
    or double quotation marks, which is useful if the value contains a
    “#” comment character.

Fixes #2405

mysql_user and mysql_db both take a login_unix_socket option.

This patch adds docs that describe how to use it.

When using a .my.cnf file, when there is no user variable defined,
default to the login user.

This change has the mysql_user module behavior match the behavior
of the mysql command-line client.

Also adds an example .my.cnf to the docs.

According to the MySQL docs[0] the password should be stored after
'password=' instead of 'pass='.

[0] http://dev.mysql.com/doc/refman/5.1/en/password-security-user.html

Fix for #1577 (python 2.4 compliance for mysql_user), tested only for syntax, please exercise MySQL fans!

- proper checking for with grant option (if this is not the only option the user has)
- added revoking of grant option

 - added terse syntax to modules.rst
 - added description of special variables to template module

  - .rst now supresses default if none is set (looks better in HTML)
  - .rst now handles empty options list
  - Fixed postgresql_user and mysql_user because YAML contained colons
  - docs for facter

Changing the parameter names to be consistent, and adding root user default with empty password, as per mysql standard

Check file exists instead of relying on the exception. Leave the exception catch in, in case the file is deleted or some other issue crops up

Changing to read from a file pointer instead so that an exception is thrown if the file doesn't exist