Fix for issue 217

Dropping the anonymous user created by default during the mysql installation fixes the problem and probably a good practice.

From MySQL manual page on the "grant" ddl: http://dev.mysql.com/doc/refman/5.6/en/grant.html

> If you permit anonymous users to connect to the MySQL server, you should also grant privileges to all local users as user_name@localhost. Otherwise, the anonymous user account for localhost in the mysql.user table (created during MySQL installation) is used when named users try to log in to the MySQL server from the local machine. For details, see Section 6.2.4, “Access Control, Stage 1: Connection Verification”.

And further:
"
Note

> It is a common misconception to think that, for a given user name, all rows that explicitly name that user are used first when the server attempts to find a match for the connection. This is not true. The preceding example illustrates this, where a connection from thomas.loc.gov by jeffrey is first matched not by the row containing 'jeffrey' as the User column value, but by the row with no user name. As a result, jeffrey is authenticated as an anonymous user, even though he specified a user name when connecting.
" - http://dev.mysql.com/doc/refman/5.6/en/connection-access.html

Also we have been using my_sql_install_db in the past which takes of not creating anonymous user as a best practice. From man pages : mysql_install_db(1):"No anonymous-user MySQL accounts are created."

https://github.com/bijugs/chef-bcpc/blob/f841591299bf6aea2e606a43736596fa8d752329/cookbooks/bcpc/recipes/mysql.rb#L66-L70https://github.com/bijugs/chef-bcpc/blob/f841591299bf6aea2e606a43736596fa8d752329/cookbooks/bcpc/recipes/mysql.rb#L66-L70