feat: init data quality dimensions

[benbenben2]

What

TL;DR:
introduced data quality dimensions (lib/ProductOpener/DataQualityDimensions.pm, tests/unit/dataqualitydimensions.t),
based on states and completeness (lib/ProductOpener/Products.pm),
all other changes are consequences of these changes.

discussion

1. redundancy between states and data quality info-> changes: moved all states into quality info, except pro platform related tests (en:to-be-exported, en:to-be-automatically-exported). "# On the producers platform, keep track of which products have changes to be exported" not sure what to do with that

2. strange with steps in the actual implementation and half steps divided by 4 -> changes: increment everything we check and divided passed tests by total count. Note that with previous implementation if all tests pass the score is 1.1

3. typo packaging -> packagings

4. packaging-code (emb) should be only for EU product and for products from animal origin

5. ingredients should be extended for all selected languages. Picture for ingredients as well.

6. en:checked is for accuracy dimension and not for completeness

7. origins: refers to "Origin of ingredients" not "Origin of the product and/or its ingredients (English)" and not "countries where sold" this is very rarely input. changes: removed this check.

8. $notempty can be replaced by the completeness score itself, if the score is 0 notempty is also 0. changes: removed this state.

9. completed_t, why to have this field? 1) poor chance to have all complete 2) what does it bring? 3) there should be another dashboard separately to see the score overtime, this dashboard would replace that field. changes: removed this field.

10. removed "en:complete" from gen_sugar/gen_sucres as it seems not working, the following 2 products appeared in the game but do not contain complete
    https://world.openfoodfacts.org/api/v2/product/6001052001018
    https://world.openfoodfacts.org/api/v2/product/5038862130530

Screenshot

Related issue(s) and discussion

• Fixes #-none-

[codecov-commenter]

❌ 26 Tests Failed:

Tests completed	Failed	Passed	Skipped
7264	26	7238	0

View the top 3 failed test(s) by shortest run time

tests_integration_export_t::0017 - export_database - 3770013801303

Stack Traces | 0.0119s run time

not ok 0017 - export_database - 3770013801303

tests_integration_export_t::0015 - export_database - 3661344653573

Stack Traces | 0.0122s run time

not ok 0015 - export_database - 3661344653573

tests_integration_export_t::0026 - export_database - 9002355004345

Stack Traces | 0.0126s run time

not ok 0026 - export_database - 9002355004345

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[benbenben2]

/update_tests_results

[benbenben2]

/update_tests_results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud