fix: use ingredient list if lang != lc to parse ingredients

[raphael0202]

Solves #5546.

As we add a new field, many expected results files are updated.
Many changes are added to search expected results files, but most of them don't seem to be due to the changes added in this PR.

[codecov-commenter]

Codecov Report

Merging #8855 (379ab9c) into main (f7905b8) will increase coverage by 0.02%.
Report is 5 commits behind head on main.
The diff coverage is 92.56%.

@@            Coverage Diff             @@
##             main    #8855      +/-   ##
==========================================
+ Coverage   48.67%   48.70%   +0.02%     
==========================================
  Files         118      118              
  Lines       22044    22060      +16     
  Branches     4899     4901       +2     
==========================================
+ Hits        10730    10744      +14     
- Misses      10010    10011       +1     
- Partials     1304     1305       +1     

Files Changed	Coverage Δ
lib/ProductOpener/Display.pm	9.94% <0.00%> (-0.01%)	⬇️
lib/ProductOpener/KnowledgePanels.pm	11.44% <0.00%> (ø)
lib/ProductOpener/Ingredients.pm	91.12% <95.10%> (+0.01%)	⬆️
lib/ProductOpener/Products.pm	42.67% <100.00%> (+0.04%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[stephanegigandet]

Many changes are added to search expected results files, but most of them don't seem to be due to the changes added in this PR.

Those changes are due to the way we construct the products to be searched on, by calling the API with values like:

	{
		%{dclone(\%default_product_form)},
		(
			code => '200000000039',
			lang => "es",
			product_name => "Vegan Test Snack",
			generic_name => "Tester",
			ingredients_text => "apple, water, palm oil",
			origin => "spain",
			categories => "snacks"
		)
	},

There's a bug in the API, and this results in "ingredients_text" + "ingredients_text_en" to be set with "apple, water, palm oil".

With the existing code, we assume "ingredients_text" is in Spanish (because of the lang set to "es"). With your code, we don't look at ingredients_text and instead see the "ingredients_text_en" and assume it is in English.

[stephanegigandet]

I'll fix the API bug.

[stephanegigandet]

Could you add a couple of tests cases specifically for this new feature?

[stephanegigandet]

@raphael0202 This should fix the test differences in search: #8877

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[stephanegigandet]

Looks good to me