fix #306603: Measure number vertical offset interpreted incorrectly

[ecstrema]

Resolves: https://musescore.org/en/node/306603

See this comment for details

• I signed CLA
• I made sure the code in the PR follows the coding rules
• I made sure the code compiles on my machine
• I made sure there are no unnecessary changes in the code
• I made sure the title of the PR reflects the core meaning of the issue you are solving
• I made sure the commit message(s) contain a description and answer the question "Why do those changes fix that particular issue?" or "Why are those changes really necessary as improvements?"
• I made sure the commit message title starts with "fix #424242:" if there is a related issue
• I created the test (mtest, vtest, script test) to verify the changes I made

[mattmcclinch]

Why such a big change to editstyle.ui? Just add the lines you need and maybe change some row numbers.

[MarcSabatella]

Tested and works as expected, thanks!

[ecstrema]

Marked as wip because the offset for above is still used when importing measure numbers with pos below...
Working on it right now.

@mattmcclinch it's true that there's more line changes than needed in editstyle.ui, but that's because of qtcreator, and by using .ui files, we accept that qtcreator saves as he likes the file. I could modify it, but it would take more time than it should and for a little bit more than 100 lines, I don't think it's needed.

[mattmcclinch]

I went ahead and cleaned up your changes to editstyle.ui. The result is not only a much nicer diff, but also a slightly improved layout, in my opinion. Here are some screen shots for comparison.

Prior to this PR:

Your proposed changes:

My proposed changes:

[MarcSabatella]

Definitely nicer, thanks for that, @mattmcclinch .

It's "OK" as is but would be much better with that change.

[ecstrema]

Thank you! You are right, it is nicer that way.

[ecstrema]

@mattmcclinch I rebased with your version. Thanks again!