Remove tune matching from best knowledge model

[awegsche]

there were two issues:

• if we match the tunes, MQT settings will be overwritten and it's not our 'best knowledge' anymore
• the tune matching calls USE internally, which deletes the b2 errors

[JoschD]

Will there be any problem if we only use the b2 but don't extract the MQTs? We will not have a matched tune then?
In omc3 we now say we always have to extract MQTs, right?
Maybe for python3: Wouldn't it make sense to make an if with a USE_EXTRACTED_MQTS parameter and extract the MQTs via the model creator instead of the GUI when needed?

[awegsche]

After discussion, I will add an ESAVE for debugging purposes