Order of selection/deletion influences resultant musical time when removing multiple time signatures

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

1. Create a new empty score from the Treble Clef template.
2. Add a 3/4 time signature to bar 3, and a 4/4 time signature to bar 4.
3. Show multimeasure rests (Ctrl+Shift+M).
4. Delete first the 3/4 time signature, then delete the 4/4. Total number of bars is 33. Undo x2.
5. Delete first the 4/4 time signature, then delete the 3/4. Total number of bars is 32. Undo x2.
6. Select first the 3/4 time signature, then the 4/4 and delete them both. Total number of bars is 43. Undo.
7. Select first the 4/4 time signature, then the 3/4 and delete them both. Total number of bars is 32. Undo.
8. Save and reload the score.
9. Delete first the 3/4 time signature, then delete the 4/4. Total number of bars is 32. Undo x2.
10. Delete first the 4/4 time signature, then delete the 3/4. Total number of bars is 32. Undo x2.
11. Select first the 3/4 time signature, then the 4/4 and delete them both. Total number of bars is 42. Undo.
12. Select first the 4/4 time signature, then the 3/4 and delete them both. Total number of bars is 32.

I.e., depending on the order of selection, deletion, and if the score has been saved and reloaded or not - I can end up with 32, 33, 42 or 43 bars from removing these two time signatures.

Supporting files, videos and screenshots

In a new score:

https://github.com/user-attachments/assets/d4d9f97b-5c52-44b5-a419-93309a1cdde8

After saving and reloading:

https://github.com/user-attachments/assets/2f82b836-7b28-43ea-a693-d9b73cf90afc

In which versions of MuseScore Studio is this issue present?

MuseScore Studio version (64-bit): 5.0.0-260211154, revision: github-musescore-musescore-60a3ec3

Regression

No.

Operating system

Ubuntu 24.04.3 LTS, Arch.: x86_64

Additional context

No response

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible