'Musical symbols scale' option & more

[XiaoMigros]

Resolves: #19366, #17885

This PR changes the following:

• An option for tuplets to use SMuFL number symbols, rather than plain text
• Pedal line text now uses the musical symbols font instead of musical text font.
• A new text style property, 'Musical symbols scale', to control the size of musical symbols in text-based elements (similar to the existing control for dynamics). This option is available for tuplets, ottava, and pedal lines.

---

For tuplets, should the using symbols be the default?

[its-not-nice]

It should, but it also needs to have a 'Scale' parameter for when people resize them (where the default 100% = 20pt) - like how dynamics now work. When we did dynamics we removed the 'Dynamics' text style (so all settings are now in Style > Dynamics) but we can't do that here because we need to keep the option to use any text font for tuplets. So there's a design question about how to arrange these settings, which are now split between Style > Tuplets and Style > Text styles > Tuplet.

[XiaoMigros]

FWIW, the scale is still influenced by the font size.

[its-not-nice]

Well it shouldn't, and I've just finished writing my comment about that on the other PR

[XiaoMigros]

Needs rebasing, closing...

[Jojo-Schmitz]

You can rebase without closing: git pull --rebase upstream master; git push -f

[XiaoMigros]

It changed my commit order, and as a consequence I could no longer force push the actual changes to the same commit as I had been doing previously.

[cbjeukendrup]

It doesn't really matter at all, but just as a hint for the future: force-pushing is something you do with a branch, not with a commit. What you probably mean is that you wanted to amend the same commit again and again. Indeed, amending the last commit is easier than amending a non-last commit, but even the latter is possible using an interactive rebase.
So, you can always force-push a branch, and you can also amend any commit except that amending the last commit is much easier than any other commit.
However, it seems strange that a rebase changed the order of your commits. A few things to make sure:

• make sure you are rebasing rather than merging. When using git pull, explicitly specify --rebase. Merging creates a merge commit that can indeed get in the way inconveniently.
• make sure you are pulling from upstream rather than origin, and make sure that upstream points to the musescore/MuseScore repo and not to the XiaoMigros/MuseScore repo.

Anyway, as said, there's not really a problem but I thought you might be happy to know these things for the future.