Incorrect scaling of sound flags icon

[MarcSabatella]

Issue type

UI bug (incorrect info or interface appearance)

Bug description

On one of my systems - a Linux container running on a Chromebook - the sound flags icon is scaled incorrectly - too large to fit within its allotted space. This is different from everything else in the GUI, which I do manage to have scale correctly via a couple of different workarounds.

Steps to reproduce

1. Add a staff text on a Muse Sounds instrument
2. Examine the sound flags icon

Result: differs depending on the screen resolution and display & scaling options used (eg, QT_SCALE_FACTOR). These issues are present on this system in both 4.3.2 and master, but I'm focusing on master here.

Screenshots/Screen recordings

Here is how it looks by default for me:

On my system, I need to set QT_SCALE_FACTOR=1.25 to get the GUI sized correctly (otherwise icons etc. are all too small. If I do only that much, the sound flag icon doesn't change. But, this isn't enough to get the score itself to scale directly. To do that, I need to run MU4 under a special Chromebook command called "sommelier" that handles the display interactions, with a command-line switch to explicitly specify the display DPI. If I do that ("sommelier -X --dpi=157 mscore4portablenightly"), then the score and icon do display correctly:

Unfortunately, this doesn't scale the GUI - only the score. So I need to combine it with QT_SCALE_FACTOR=1.25 in order to get both the UI and score to scale correctly. When I do that, the sound flag icon continues to looks correct in master:

But it looks noticeably worse when I do the same in 4.3.2, which is how this got noticed by @avvvvve in one of my demonstration videos in the first place:

Apparently this is the first use of the MuseScoreIcon font directly within the score view. No idea if any of this would be reproducible on any system other than a Chromebook with a high DPI using these particular workarounds for the more general scaling issues that are always present. Which to me are a much bigger concern; see an issue I filed prior to the release of 4.0 - https://github.com/musescore/MuseScore/issues/10458. But I recognize it doesn't seem to affect many other users.

So anyhow, make of this what you will, and I'm happy to run additional tests if you have other ideas of things I should try!

MuseScore Version

OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.0-241760505, revision: github-musescore-musescore-5203474

Regression

I don't know

Operating system

Debian 12

Additional context

No response