Node Tools: Add mouse potiion node, wait for cursor option

Add a "Mouse Position" node that outputs the location of the mouse
cursor in region space and the overall size of the region, both in pixel
units. Both outputs are integers to help reflect their pixel units.
If there the mouse position is ever accessible in sub-pixels, they can
easily be changed to floats.

Also add a "Wait for Cursor" option similar to the one for some built-in
operators that delay's the operator's execution until there is a mouse
click in the viewport. That way the operator can be called from menus
even though it is interactive. This option is placed in the node editor
header. When there are more options, it will be part of an "Options"
popover panel similar to the existing "Modes" and "types" popovers.

Combined with the viewport transform node, and other nodes like Raycast,
these features can allow making tools that create geometry where you
click in the scene.

@@ -171,6 +171,7 @@ class NODE_HT_header(Header):
                 if snode.node_tree:
                     layout.popover(panel="NODE_PT_geometry_node_tool_object_types", text="Types")
                     layout.popover(panel="NODE_PT_geometry_node_tool_mode", text="Modes")
+                    layout.prop(snode.node_tree, "use_wait_for_cursor")

@@ -471,2 +472,4 @@
     operator_eval_data.self_object_orig = object;
     operator_eval_data.scene_orig = scene;
+    RNA_int_get_array(op->ptr, "mouse_position", operator_eval_data.mouse_position);
+    operator_eval_data.region_size = int2(region->sizex, region->sizey);

@@ -0,0 +8,4 @@
+
+static void node_declare(NodeDeclarationBuilder &b)
+{
+  b.add_output<decl::Int>("Mouse X");

@@ -0,0 +12,4 @@
+      "The region-space mouse X location, in pixels, increasing from 0 at the left");
+  b.add_output<decl::Int>("Mouse Y").description(
+      "The region-space mouse Y location, in pixels, increasing from 0 at the bottom");
+  b.add_output<decl::Int>("Region Width").description("The total X size of the region in pixels");