Fix #32396 : Bugs in TAB note inputs.

Several inconsistencies accumulated in TAB note input during recent updates.

The main point is that currently the pitch, fret and string of a note -- if all are known -- must be changed in a single step; otherwise, the fretting algorithm intervening after each step notices they are inconsistent and refrets (potentially) the whole chord, which leads to loosing the fretting entered by the user.

A specific `undoChangeFretting()` function has been added, to be used with TAB's instead of `undoChangePitch()` when all the new fretting data (pitch, fret and string) are known in advance.

Also, the fretting algorithm has been changed to be more conservative, i.e. to keep the current note fretting (potentially entered by the user) as much as possible.
Fix most issues for continuous view panel
Fix #32261 : Local edit of bar line affects all bar lines

The use case detailed in the original issue (http://musescore.org/en/node/32261) was the following:

If edit mode is entered for a bar line with user-edit span (e.g. a tick) and then exited without any edit, as Ctrl has never been pressed, the edit is assumed to be global and the span of all the bar lines is changed to that specific bar line span.

Adds the following fixes:

- Entering and exiting bar line edit mode and doing nothing actually does nothing whatsoever.
- Any further span edit of a bar line whose span is already user-customized is assumed to be local to that bar line only. This makes using [Ctrl] for any further editing of a single bar line redundant.

Additionally:

- Any change in the span of system-initial bar line is always assumed to be local and no longer affects all the bar lines, as before.
Adds to the Articulation class 4 symbols for lute tablature fingerings.

The Articulation class has been chosen because these symbols behave much like other articulations. The class already contains a number of symbols which are not really neither articulations or ornaments.

The new symbols have been grouped together with the somehow related cello thumb position symbol, at the end of the ArticulationType enum and set to `ArticulationShowIn::TABLATURE` only.

A specific case for them has been added in the `Chord::layoutArticulation()` method, as they do not follow the rules of other articulations.
fix #32161: false collisions with crossstaff notes
Further color changes
Brighter colors, as requested
fix #32331: lower case minor chord issues on save/reload
fix #32471: crash on setting drumset note to auto
fix #32416: crash on note entry in voice>1 at end of score
update Gonville, add GonvilleText

fallback to BravuraText
add vtests for Gonville

modeled after the Bravura tests
update vtests for Emmentaler and Bravura
Merge pull request #1295 from MarcSabatella/32416-last-tie-crash

fix #32416: crash on note entry in voice>1 at end of score
Merge pull request #1291 from MarcSabatella/32161-staffmove-collision

fix #32161: false collisions with crossstaff notes
Merge pull request #1293 from MarcSabatella/32331-lower-harmony

fix #32331: lower case minor chord issues on save/reload
Merge pull request #1287 from vgstef/ContinuousPanel

Fix most issues for continuous view panel
Merge pull request #1294 from MarcSabatella/32471-drumset-auto

fix #32471: crash on setting drumset note to auto
Merge pull request #838 from Jojo-Schmitz/gonville-vtest

update for Gonville and vtests
Merge pull request #1292 from mirek2/color-scheme

Brighter colors