Separate nav graphs for CleanerBotA and CleanerBotE

[Yadunund]

Bug fix

Fixed bug

Previously both cleaning fleets shared the same traffic map and hence nav graph which included 4 cleaning zones. CleanerBotA was configured to clean all four zones but CleanerBotE, only zones 2, 3 & 4. But this constraint was enforced by the way the DockSummary message was being populated by the mock_docker node. However, a user could submit a loop request with start waypoint as zone_1 which could then get assigned to CleanerBotE as the waypoint exists in its nav graph (same nav graph). When the robot enters the lanes with zone_1, it would begin docking process at which stage the robot will be stuck forever (as mock_docker cannot find the list of docking waypoints for zone_1 for CleanerBotE).

Fix applied

Separated nav graphs for the two fleets.

Nav graph for CleanerBotA (deleted lanes that access charging points of CleanerBotE)

Nav graph for CleanerBotE (deleted lanes that access zone_1 and charger point of CleanerBotA)

Also disabled loop requests for both fleets.