Issue #1317554 by smokris, FatGuyLaughing, jarodms, and klausi: bringing the 6.x branch to a basically-usable state

Enhanced the role_export_roles() cache function to do extra checking to see if there has been a machine_name created. Take the proper actions if no machine_name is present. Utilize the hook_init() function to call our role_export_roles() cache function. This will fire every page load, however will always return a cached version of the roles unless cache has been cleared. During the installation of a feature will clear the cache and cause the role_export_roles() cache to rebuild getting the new data and fixing the data if needed before saving back it back into the db and cache.

When deleting a role the role_export_roles cache gets cleared. This gets rid of the bug of ghost machine_names existing. Updated the drupal_write_record() to a db_query(). We have to use the db_query() because we are not only updating the role information but also overriding the role id. Which can not be done in drupal_write_record().

Removed the db_add_unique_key(). This would need to be done via the user module. We have validation on the role entry form. Only way a user could have duplicate machine_names is because they used a query to do it.

Fixed all the issues with the initial port except the role machine_name generation of roles being created via the features api or another round about way.