[3.x] Node Selection and Positioning Delay Issue

### Tested versions

v3.7.dev.custom_build [5155fe5a4]

### System information

w10 64

### Issue description

Watch the video. When you click on a node, it takes some time for the node to appear as selected, even though it is already selected in reality.

I noticed that if you move the node, it lags behind the cursor, and the node is positioned with a delay.

If you wait for the node to be fully selected, it then correctly positions itself at the cursor’s location.

My report is asking if it’s possible to eliminate or optimize the selection delay that must be waited for before the node positions correctly at the cursor.

I’m not sure if this is a bug or what exactly is happening.
It seems to be related to the complexity of the script assigned to the node. Nodes with scripts that have little code are selected faster.
As you can see in my video showing Godot 4, this problem doesn't happen, but as I mentioned earlier, it's probably because the node that moves in Godot 4 doesn't have a complex script.

Video of v3.7.dev.custom_build [5155fe5a4]

https://github.com/user-attachments/assets/f87fc52d-f2ea-4952-934e-9778c8da3c38

Video of godot 4

https://github.com/user-attachments/assets/adc4d5cd-2243-4d85-b831-52276195017e

### Steps to reproduce

See the video of godot 3

### Minimal reproduction project (MRP)

...

Start by reproducing the behavior from the Godot 3 video using a node with a complex script, then compare it with the Godot 4 video. No source files, tests, or minimal reproduction project are identified; done means identifying the selection or positioning delay and confirming that node movement follows the cursor without waiting.

Written by the indexing model from the issue text.