Approved context changes to Hungarian translation, updated changelog. Bumped to version 1.5.2-alpha3

(grafted from bd7a82ad06fa8913b3d529b41d218495d2b406b8)

Added logic to set bowing when bandoneon note is selected and to set bellow state depends on score bowing symbol

Added technical data to note object, implement string number and bowing symbols, fingering maybe later

Added class for storing extra note data (guitar position, fingering, bow direction/bellow open/close). Use it in chunk instead of single TfingerPos.

Increase radius for popup background to improve visibility, create dialog loader on demand - reduces launch time a little

Use integer type as a data transport value for extra information about note - like position on a guitar or bandoneon related. So TcommonInstrument has virtual method askQuestion and noteData to set and get those information from instrument instance. For piano and sax this is unused. Executor finally can set and get guitar position.

Added note prompt for single note to point where to select note, when score is cleared clear key signature as well, when exam starts - revert colors of note 2 and 3

Properly play newly added note, hide note cursor when clicked to show what note was selected, properly hide note names when single note is on

Checking answer (partially), displaying results so added ResultTip.qml and all signals. Restore tresulttexts and textrans

Reset note item state when score switches from single mode instead settings those default props when note is re-created (taken from storage). It fixes crash, because with previous approach the note item has no staff set to perform all required settings.

Name control can change name style for buttons and displayed text separately (executor uses it). Also accidental and octave buttons can be set without invoking name text change (when note is invalid). When it is disabled all buttons are unchecked. Refresh name text when 'show enharmonic notes' changes

Avoid adding control in single note mode, properly lock key signature and adding control. Call question tip with delay to avoid animation collision with expensive initializing of sound.

Create note cursor and adding/deleting controls on demand. TaddObject calls add note directly from score object instead of emitting signal to QML

Do not depend on Tglobals, add quick overload of setNote method, access TnoteObject directly through TscoreObject::note(index) instead of TnotePair::item()

Unlock key signature when needed, added keyReadOnly property to score object, so executor can set it when necessary. Also AccidConrol.qml depends on notify-able cursorAlter property of score object (previously there was opposite) - this way force accidentals by executor could be implemented. Display confirm tip as well. Display fake key sign. - use keyName of MainScore.qml position for it

Create and display question mark on the score (centered in score background rect), so make TscoreObject::component() and TscoreObject::qmlEngine() public methods to use them in main score object

Redirect TscoreObject methods in TmainScoreObject, use them in executor. Exclude code of setting melody notes to score to separate method TscoreObject::setMelody(Tmelody*) to use it during asking questions

Manage key signatures value and enabling/disabling it only through score object, so score.keySignature is just alias to TscoreObject property. All dependent things on QML side adjust itself to it. There is less JS stuff that way.

Score clef is accessible just through single variable either from QML or C++, get rid double calls in controls using score component. Use more declarative approach in QML score implementation (direct binding of score.clef instead of functions)

Create score menu on demand only, so exclude it to separate file, use TipRect as a background item (also for TempoMenu).

Create object helper with C++ logic for main score. Actions are created there and it provides score actions list for a menu

QML score functions (setNote, addNote, clearScore, deleteLastNote)can be invoked through score object directly, so there is no necessity to call them through meta object. A few signals were added to perform QML routines when C++ part is done.