ldapBackend.py: Do user.save() after user-create's add-group

* When a user doesn't exist and needs to be populated from ldap, the
  user.save() is located inside the conditional code for setting
  LDAP_AUTH_GROUP. This commit moves it after that so the save() always
  happens (even if LDAP_AUTH_GROUP is set in settings.py it might bork
  before the save() if the group doesn't exist).

* Also moved it and the user.is_active assignment to after the
  "user-exists" try-except block, to be more DRY
Merge pull request #68 from rowanthorpe/fix-ldap-user-creation

ldapBackend.py: Do user.save() after user-create's add-group

LGTM. As a side note, I will be visiting this backend a bit more soon. I already got some unit tests for it and will try to increase them both to increase code coverage as well as traverse unvisited code paths to expose bugs. Thank you