PR candidates to be merged to MuseScore 3.3 Beta 2

[anatoly-os]

Pull requests in the list fix the P0 and P1 issues from the issue tracker or were suggested by the community or selected by in-house team.

• [MU4] Update to latest SMuFL version 1.3 #4883 (unclear motivation)
• Update Bravura and BravuraText to latest Steinberg version 1.32 #4879 (unclear motivation)
• (Based on #5221) Accessibility fixes. Part 4 #5270
• Add button to move soundfont to top #5269 (needs manual testing and cherry-picking changes)
• Fix #293017: Plugin: Enable elements selection from plugins #5259 (selection is an error-prone field)
• integrate changes for WINSTORE #5214 (affects only WINSTORE builds, not relevant now)
• Clean up some temp files after they are not needed anymore #3163 (work in progress, unaddressed review, needs thorough testing, not urgent?)
• fix #271445: allow MusicXML export with .xml extension #4370 (unclear motivation)
• 279877 continuousview #5255 (unaddressed review)
• fix #287662: transpose keys #4916
• fix #23187: Change UI in preferences for exporting musicxml #4443 (unaddressed review, rebase needed)
• fix MSVC/MinGW compiler warnings #5291
• fix #293707: undo doesn't restore deleted frame immediately #5293
• fix #293897: [Tablature] Note value repeat section: setting "Never" broken #5295
• fix #289374: tuplet numbers: 'follow staff size' not working #5037 (rebase needed)
• fix #294006: Symphony Orchestra template has wrong patches for pizzicato #5297
• fix #288169, #287889: draw lines when there are two hooks and draw hooks solid #4957

Included to MuseScore 3.3 Beta 2:

[Jojo-Schmitz]

Please consider #5291 and #5297

[jthistle]

I very much like that we're organizing things like this, but GitHub does provide the 'milestone' feature for exactly things like this - maybe it would make it slightly easier to do it like that for the next milestone? Just an idea :)

[anatoly-os]

@jthistle I tried to organise the project, but it was something different. I'll take a look, thanks!

[jthistle]

Yes, projects are more for full workflows, i.e. you put a bug in the first column, someone takes it on and moves it to the next column, when it's fixed it gets moved on and so on. It works well for smaller projects, but isn't really what we want here, AFAIK. Milestones seem like exactly what we might want though; it's just a way of tagging PRs to be merged for a specific date/version.

[mattmcclinch]

Please also consider #5295, as it fixes a recent regression.

[Harmoniker1]

#5300, #5303 and #5315 all do some non-trivial improvement. I hope you can consider them.

[DLLarson]

#5259 has the comment "selection is an error-prone field".

How so? It's an additive feature so can't break existing code. The code changes are not complex.

No inspection comments have been made to support this judgement.

-Dale