bugfix(view): Recalculate Camera Area Constraints when toggling Control Bar or changing Pitch, FOV

[xezon]

This change recalculates the Camera Area Constraints when toggling the Control Bar or changing Camera Pitch or FOV. Right now Pitch and FOV can only be changed in Debug. But it will become available in Release in the future.

The Camera Area Constraints are responsible for binding the camera into the visible map area, preventing the player from scrolling into oblivion.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR fixes a bug where camera area constraints were not being recalculated when the viewport dimensions changed (toggling control bar) or when camera properties like pitch and FOV were modified. The fix properly invalidates m_cameraAreaConstraintsValid in all relevant functions, ensuring that the camera boundary calculations are updated to reflect the new viewport or camera configuration.

The changes follow the existing pattern used throughout the codebase where m_cameraAreaConstraintsValid is set to false alongside m_recalcCamera = true whenever camera properties change. The implementation is consistent with other camera modification functions like forceRedraw(), setCameraHomePosition(), and various camera movement functions.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes follow an established and consistent pattern used throughout the codebase. Setting m_cameraAreaConstraintsValid = false is the standard way to invalidate camera constraints, and this flag is properly checked and recalculated in the render loop. The bug fix addresses a legitimate issue where viewport changes weren't triggering constraint recalculation.
• No files require special attention

Important Files Changed

Filename	Overview
Core/GameEngineDevice/Source/W3DDevice/GameClient/W3DView.cpp	Adds m_cameraAreaConstraintsValid = false to invalidate camera constraints when viewport dimensions or camera properties change, ensuring constraints are recalculated properly

[Mauller]

Sense it makes

[Skyaero42]

Add empty line before comment

[xezon]

Negative. A future change will remove the lines above. That is why it looks cramped right now.