Fix #27678: Don't reset marker label on style change

[XiaoMigros]

Resolves: #27678

Removing this method seems to have no adverse effects, and since jumps don't have one either it should be safe.

• 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)

[zacjansheski]

Changing the label of Segno survives changing styles, but does not survive save and reopen file

video1227348117.mp4

[JamesBrigham-MS]

I have this issue in the context of a 2nd Coda label change which is lost after saving.

If using a 2nd coda in a piece that needs to be labelled other than the default codab, it reverts back to codab once the piece has been saved, closed and re-opened.
The label of the respective D.C. al Coda is not affected.
The jump to the re-labelled coda works at first when the new label is newly applied so the setup of the coda appears to be correct and functioning.

I came across this when updating my upload of Dizzy Fingers. I had attempted to copy and paste my work into a new file in MS4.6.4 but realised the final coda wouldn't keep its new label as it had before so reverted to my old version which has a creation date of Sat May 23 2015

In my current upload of Dizzy Fingers the jump to the final coda works seemingly because I have stuck with the file originally created in MuseScore 2.3.2 yet have edited it in MS 4.6.4
If you view the playback of Dizzy Fingers from bar 63 you will see that it plays the A strain before correctly jumping to bar 64 - yet this appears to be impossible to setup in a newly created MS4.6.4 file.