Scripts/Instances: Complete rewrite of the boundary system.

- Migrate boundary logic to Maps/AreaBoundary instead of having it sit in InstanceScript (to possibly allow use for other purposes).
- Implement the first five boundary types in Maps/AreaBoundary.cpp.
- Add boundary checks to Creature's update logic
- Add boundary data for all Northrend raids
- Add boundary initialization structures and methods to InstanceScript
- Modify EnterEvadeMode signature. It now passes a value from the EvadeReason enum as parameter to allow special casing depending on evade reason
- Remove previous (weird) boundary code that had them linked to GO spawns

sql/updates/auth/2015_12_21_boundary.sql

@@ -0,0 +1,6 @@
+--
+DELETE FROM `rbac_permissions` WHERE `id`=836;
+INSERT INTO `rbac_permissions` (`id`,`name`) VALUES (836,"Command: .debug boundary");
+
+DELETE FROM `rbac_linked_permissions` WHERE `linkedId`=836;
+INSERT INTO `rbac_linked_permissions` (`id`,`linkedId`) VALUES (196, 836);

sql/updates/world/2015_12_21_boundary.sql

@@ -0,0 +1,10 @@
+--
+DELETE FROM `command` WHERE `permission`=836;
+INSERT INTO `command` (`name`,`permission`,`help`) VALUES ("debug boundary",836,"Syntax: .debug boundary [fill] [duration]
+Flood fills the targeted unit's movement boundary and marks the edge of said boundary with debug creatures.\nSpecify 'fill' as first parameter to fill the entire area with debug creatures.");
+
+DELETE FROM `trinity_string` WHERE `entry` IN (11011,11012,11013);
+INSERT INTO `trinity_string` (`entry`,`content_default`) VALUES
+(11011,"VisualizeBoundary warning: No interior point of the creature's boundary could be found - check if you have mutually exclusive boundaries!"),
+(11012,"VisualizeBoundary error: Creature movement is unbounded"),
+(11013,"VisualizeBoundary warning: Reached fail-safe flood boundary - check is your boundary is unbounded!");