Fix Swing and Straight markings format #27188

[cheilagoncalves]

Called the function initTextStyleType to load the corresponding text style values.

Resolves: #27188

The Swing and Straight markings weren't formatted correctly in the Tempo and Masters palette like the rest of the elements in the section. This occurred because real Tempo texts automatically take the format because of the textStyleType, but since Swing and Straight
elements are simple SystemTexts I add to call the function initTextStyleType so it could load the corresponding text style values.

• 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

[cbjeukendrup]

The VTests failed; this should be fixed after a rebase, to integrate the latest changes from the master branch.
git pull --rebase upstream master; git push -f
Also, if you could squash the commits into one, that would be great in this case (since these changes are small enough to fit in one commit).

[cheilagoncalves]

The VTests failed; this should be fixed after a rebase, to integrate the latest changes from the master branch. git pull --rebase upstream master; git push -f Also, if you could squash the commits into one, that would be great in this case (since these changes are small enough to fit in one commit).

Thank you, I'll submit these changes!

[zacjansheski]

Tested on MacOS 15, Windows 11, Ubuntu 22.04.3. Approved
#27188 FIXED

[FrancRos31]

Is this PR going to solve #26271, too?

[cbjeukendrup]

No, this is only about the text weight of those two particular cells.

[cheilagoncalves]

Thank you so much for approving my pr!

[Jojo-Schmitz]

Shoudln't that go to 4.5.2 too?

[cbjeukendrup]

It could. @cheilagoncalves perhaps that's nice, because then your work will soon be visible to the world.

We can port the PR to the 4.5.2 branch for you, but maybe you would like to do it yourself:

1. Checkout the 4.5.2 branch
2. Create a new branch based on it (you can choose any name you want, for example port/4.5/swing_straight_text_format)
3. Cherry-pick the commit from this PR to that new branch (as you can see on this page, the commit SHA is afae820, so you can run git cherry-pick afae820)
4. Create a PR from that branch, but then on GitHub, instead of setting the base branch to musescore:master, set it to musescore:4.5.2.

[Jojo-Schmitz]

Done, see #27697