Initial call to RenderGraph::resized() causes RenderGraph.renderArea to be zeroed out

[dov]

Describe the bug

After calling renderGraph->resized() the first time, the value of renderGraph.renderArea = {{0,0},{0,0}}.

To Reproduce

1. Modify vsgoffscreenshot.cpp as follows:

                 offscreenRenderGraph->resized();
+                vsg::info("offscreenRenderGraph->renderArea=(",
+                          offscreenRenderGraph->renderArea.offset.x, ",",
+                          offscreenRenderGraph->renderArea.offset.y, "),(",
+                          offscreenRenderGraph->renderArea.extent.width, ",",
+                          offscreenRenderGraph->renderArea.extent.height, ")");

2. Compile and run
3. Resize the window
4. Press 'e'

Expected behavior
The offscreenRenderGraph->renderArea should be equal to the offscreenExtent.

Screenshots
Not relevant

Desktop (please complete the following information):

• OS: Fedora Linux 41

Additional context
The zeroed out renderArea may cause subsequential vulkan validation errors of the type:

VUID-VkRenderPassBeginInfo-None-08996(ERROR / SPEC): msgNum: 1495210966 - Validation Error:
  [ VUID-VkRenderPassBeginInfo-None-08996 ] Object 0: handle = 0x2b3bf510,
  type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x591f1bd6 | vkCmdBeginRenderPass():
  pRenderPassBegin->renderArea.extent.width is zero.
The Vulkan spec states: If the pNext chain does not contain VkDeviceGroupRenderPassBeginInfo
  or its deviceRenderAreaCount member is equal to 0, renderArea.extent.width must be greater
  than 0 (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkRenderPassBeginInfo-None-08996)

I admit that I don't understand why it does not always happen.

The reason for the zeroed out renderArea seems to be due to the uninitialized variable WindowResizeHandler.previous_extent.