finalize User, Contact and UserTrait business logic

[basejump]

for separation of concerns, the security plugin has a AppUser domain that does not depend on contact.
Rally has a Contact domain for the Contacts under Org.

• When it comes to Rally, should the relationship be enforced so that a User is a Contact?
• Currently Users are being created without enforcing contact.
• There are a number of domains that have Contact that might need to be replaced with AppUser. See Activity and ArTranRelated
• DisputeService relies on Contacts.
• There is logic that has tests but looks to be unfished for Customer contacts->users
• right now displayName exists on the UserTrait, so there is consitency should apply to Contact as well for areas where they would expect to see same thing (such as drop downs syncing with editeByUser.displayName)
• logic is active and in place for updating user when Contact is updated.
• currently when creating a user it does not create a contact and keep ids in sync that I can see.