ObjectConstraintManager setup
Traversing the graph & function evaluation are added
Constraints object logic is introduced to define constraints in it
To define a constraint or constraints for a model, a child object called 'Constraints' should be created in the model itself. Within the 'Constraints' object one can define as many costraints as he wants by creating elements and defining functions in the input area. Name of a constraint is used to display the statuses of validations.
OCM: Object name is added to the warning messages
constraint violation is logged as an error
Merge branch master
Constraint Manager validation is updated to match the latest changes on core
update territory functionality is added to Constraint Manager
constraint population improved
UI is removed after validation
the word 'object' is dropped, dummy dialog for constraint results is added
alert messages are shown after validations
create alert-error for priority 0
simplifying ContraintManager

no need for territory management, run only on local node + children
Merge branch 'constraint_manager' into demo

Conflicts:
	client/js/Panels/ModelEditor/ModelEditorControl.js
	client/js/WebGME.js