Fix cmdDeleteTuplet: use first element tick instead of (corrupt) tuplet tick

[manolo]

Resolves: #33360

Tuplet::tick() can return 0 on imported scores because several importers do not call setTick() on Tuplet objects, leaving Tuplet::m_tick at its default value. When cmdDeleteTuplet calls setRest(tuplet->tick(), ...) it places the replacement rest at tick 0 instead of the actual tuplet position, silently corrupting the score (notes at measure 1 beat 1 are overwritten).

Confirmed with MIDI import. Likely also affects OVE, GuitarPro and TableEdit imports, which also skip setTick() on tuplets.

Fix: save the tick from the first element BEFORE removing elements and use that instead of tuplet->tick().

• I signed the CLA
• The title of the PR describes the problem it addresses
• Each commit's message describes its purpose and effects, and references the issue it resolves
• If changes are extensive, there is a sequence of easily reviewable commits
• The code in the PR follows the coding rules
• There are no unnecessary changes
• The code compiles and runs on my machine, preferably after each commit individually
• I created a unit test or vtest to verify the changes I made (if applicable)

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[mathesoncalum]

I think we should address this in our importers and prevent the corrupted tick from happening in the first place. It shouldn't matter how a tuplet was created, the deletion implementation should be the same.

[Jojo-Schmitz]

I believe you should rebase it to main (rather than master), if alone for it to show in the issue as fixing it