PartitionManager: Add safety checks to prevent access violations in iterateCellsBreadthFirst and getNearestGroupWithValue

[seer-by-sentry]

Fixes CLIENT-S6. The issue was that: Access violation read in PartitionManager::iterateCellsBreadthFirst due to calling a member function on an invalid or uninitialized ThePartitionManager singleton instance.

• Added null checks for input parameters (pos, m_cells, proc) in iterateCellsBreadthFirst to prevent crashes.
• Added bounds checks for starting cell coordinates (cellX, cellY) in iterateCellsBreadthFirst to prevent out-of-bounds access.
• Added validation for cellCount in iterateCellsBreadthFirst to prevent invalid memory access.
• Added null check for curCell within the main loop of iterateCellsBreadthFirst.
• Added null check for m_cells in getNearestGroupWithValue.
• Added bounds check for nearestGreat before accessing m_cells in getNearestGroupWithValue.

This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 2523071

Not quite right? Click here to continue debugging with Seer.