Putting it all together from: #6979 #6977 #7060 #7066

Filters should look like:

LABELED (X%) ............... amount (Accuracy somewhere)
NON LABELED (X%) ............................ amount

Match ............. amount
Mismatch .............. amount

(OTHERS)
Obsolete ...............amount
Error.......................amount

• Three separate sections
• When a suggestion is Error or Obsolete it is not computed in the other two sections' stats
• We are removing the "no context" filter. This is going to be controlled by the service. (fixes [IX] Incorrect logic for Has Context suggestion property #7060)

We need to give support for "labeled as empty". Uwazi needs to send these empty markers along with the rest of the training data. If a property has no value, but it also does not have the empty marker, we do not send it to training.

Statuses are display on the table as:

• IF it is a select/rel field => "X values | X suggestions | X mismatching" (as it is now)
• IF it is a text/num/date => as it is now
• Labeled as empty/suggested empty becomes an explicit special case. It is not the same as an empty string. It will come like that from models and we will send it like that to models. So we can have a special icon or pill and it can say "empty" | "empty" or whatever.
• Error
• Obsolete

Models will control what comes as "segment", which can contain either the context or some other message, to be display in the column in the table. Ie. if there was an error, that row will contain the status "Error" along with the context "Couldn't read PDF file" or whatever the model decides. We don't need to run any logic on the rendering of the context, just print whatever the model is sending, if it is a blank string, so be it.