When adding a new instrument to an existing score, the staff type given in the instrument template is not observed and a standard staff is always proposed in the Instr. dlg box.

Fixed by removing a (previously needed) distinction in the list of available staff types used by the Instr. dlg box between types coming from presets and types coming from the score. This led to existing types not being found in the list.
If another staff is linked to a TAB staff, entering the 2nd digit of a 2-digit fret number has no effect in the linked staff.

Fixed by iterating the fret no. change on all the notes linked to the note being edited.

Note: is it reliable to assume that elements linked to a Note are also Note's?
Merge pull request #473 from mgavioli/Staff_type_when_adding_a_new_instr_to_an_existing_score

Staff types when adding a new instrument to an existing score
several minor UI improvements
fix #22691
fix build
Merge pull request #474 from mgavioli/obey_multidigit_fret_nos_in_staff_linked_to_tab

Obey multi-digits fret nos. in staves linked to a TAB staff
Rename Tablature class to StringData

Refactoring the following names:

Classes:
Tablature => StringData

Member variables and methods:
Instrument::tablature() => stringData()
Instrument::setTablature() => setStringdata()
InstrumentTemplate::tablature => stringData
InstrumentData::_tablature => _stringData
InstrumentData::tablature() => stringData()
InstrumentData::setTablature() => setStringData()

There is no change in logic or program behaviour, only renaming.
don't crash on unknown shortcut entry
* Fix Guitar Pro test ref. file.

* Replace "Tablature" with "StringData" in instruments.xml

* Remove support for "Tablature" tag from instrtemplate.cpp (but keep it in instrument.cpp for compatibility with existent 2.0 scores)
Merge pull request #475 from mgavioli/Rename_Tablature_class_to_StringData

Rename Tablature class to StringData