Fix issue #4794 corrected Pitch block drag-and-drop behavior to match…

[zealot-zew]

Summary

This fixes an issue where dragging a Name block out of a Pitch block and then dragging it back in caused a redundant Name block to appear, instead of the original block snapping back without duplication.

What’s fixed

Prevented addDefaultBlock() from recreating Name sub-blocks while snapping back.
Name blocks now behave like Octave blocks— detach cleanly and snap back into place.

How to test

Create a Pitch Block
Drag the Name block out- a default duplicate must appear
Drop the Name block back - it should reattach without creating any redundant Name block

Screen.Recording.2025-11-08.at.12.32.54.AM.mov

Fixes #4794
Tested on macOS (Chrome) and verified consistent behavior with Name block logic.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[zealot-zew]

apologies for the messy PR with removing spaces for no reason (my VS code extensions would have do that)

[harshrajsoni]

The Key changes is this:
if (this.blockList[parentblk].name !== "pitch") {
this.addDefaultBlock(parentblk, thisBlock, actionCheck);
}

Screen.Recording.2025-11-11.160030.mp4

I have tested the code and sorry to say that the code doen't resolve the issue... The issue still persists
@pikurasa Please look into it.
Thank You

[zealot-zew]

@harshrajsoni
The duplicate octave or name block is intended feature of Pitch block, the bug i fixed was when name block is snapped back it creates a redundant name block
please check with the reference to the issue #4794

[harshrajsoni]

but the PR is created for different issue i think
Please check that
Thank You

[zealot-zew]

@harshrajsoni
yeah youre right, i edited the wordings in my PR
check now

[walterbender]

Could you please separate your linting changes from your bug fix into two separate commits? (They can remain in the same PR.)

[walterbender]

@pikurasa do you agree with this UX change?

[walterbender]

@pikurasa we still need to discuss this one from the UX perspective.