Pasted nodes place on the same position instead of mouse position

[sami8github]

Godot version:
v3.1.dev.calinou.1800664

OS/device including version:
windows 10 x64

Issue description:
In visual script
when copy a node in visual script area and paste, Godot place it on the same place instead of mouse position.
in big visual scripts this is problem, because user will drag the nodes and pan the view many times to place the nodes correctly.

[fire]

This should be resolved by #28162

[fire]

This is a related problem, but not resolved.

[KoBeWi]

In 3.2.3 rc3 the duplicates get stacked:

So it's not strictly a bug.

EDIT:
Although seems like the nodes are pasted on the original position, so e.g. when you copy, move it and then paste, the new node will appear where the first one was previously.

[archerallstars]

This is still happening in 3.2.4 beta 4.

The pasted node(s) will not be at the user's mouse position or the current viewing area, making it useless to cut, copy, and paste nodes in a big and complex Visual Script.

This could also cause a serious problem in usability since a lot of nodes that the user intended to use elsewhere will be at the same position which might have so many nodes already, thus the reason why they were copied in the first place.

I am not sure if this issue could fit into the discussion tag since the current behavior definitely doesn't align well with the expected behavior of the cut, copy, and paste feature where the user expected to be able to control the pasted position/destination of the copied item. For instance, if they just want to copy and paste at the same place, that would be the duplication (ctrl+d).

However, with all that said. I don't think that to copy and paste a group of complex nodes to use at many places in the script is a good way to work in Visual Script. Especially, when we don't have the ability to search for a function call and a variable in Visual Script yet (proposal #1780). I think it would be more manageable if that kind of node group is converted to a function by which the differential in logic is controlled through the function's arguments.

But anyway, with this issue, it's still a problem if the user just wants to cut a lot of nodes to work with them in another place. This could be another place in the script to gain more scripting space or in another script entirely.

[Gallilus]

Possibly solved with merged PR #54564

[akien-mga]

Assuming fixed, please comment if the original issue is still reproducible in the next 4.0 build.