User info changes do not reflect in a clustered environment

[jbrojdeCTL]

If a new user is created, or workgroup/roles added/removed for a user using Hub, those changes are reflected on the instance where the changes took place, but other instances running in same cluster do not know about it until they are bounced, or their cache is refreshed. Since instances are now supposed to be agnostic as to where other instances run (i.e. such would be the case in cloud type deployments such as PCF, Mesos, Kubernetes, etc), we need to implement a way to tell other instances that user information has changed, similar to how asset imports now take place (AssetImportMonitor).

[jbrojdeCTL]

Along with implementing the new UserGroupMonitor to detect User/Workgroup/Role changes made by other instances, the AssetImportMonitor/Import functionality was also modified to use the VALUE DB table instead of the ASSET_REF table to detect imports performed in other instances in a cluster. ASSET_REF is still used the same way as before, with the exception of determining if an import needs to be triggered.