fixes #6550 / BZ 1117952 - fix issues with changing org name which affected running db:seed

Without these changes, the user cannot change the default organization
name and re-run 'rake db:seed'.  The reason being, it would attempt
to create an organization with a label that was already in use and
the seed would fail.

In order to address this, this commit does a couple of things:
1. when creating an org, if a label is automatically generated
   and it is already in use, re-generate the label using a uuid.
2. fix an existing validation which was incorrectly comparing
   name=label, label=name, etc. during org create and update.
If you use the API and do not provide a label, it will attempt to assign one based on the name; however, if it cannot due to a conflict, it will assign it to a UUID.  If, however, you use the API and do provide a label, it will generate a validation error if there is a conflict.

So, if the user really cares about the label that is going to be assigned to the object, they should attempt to provide one vs rely on the system to automatically assign it.