refactor: different taxonomy source files for flavors

[stephanegigandet]

I think this is the simplest way to allow Product Opener flavors (OFF, OBF, OPF, OPFF) to have some taxonomies that are different.

• I created /food and /beauty to put taxonomies that are specific to a product type.
• At this point I moved only the ingredients.txt and categories.txt file, and let all other taxonomies in the root directory (even if they are specific to food). This is to avoid breaking in flight PRs. Similarly, I didn't create a /common directory. We can revisit this later and move more taxonomies.
• Resulting taxonomies are build and cached as usual (in particular the resuting files will be in /taxonomies/ even for specific taxonomies).

The drawback of this approach is that one instance of Product Opener is tied to a specific product type, it can't load taxonomies for multiple types. If at some point we want to have one Product Opener instance serve multiple product types, we can revisit it as well.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[alexgarel]

If at some point we want to have one Product Opener instance serve multiple product types, we can revisit it as well.

Yes it seems to me that in our plans we spoke of having such an instance… to do later :-)

[alexgarel]

Great.

[alexgarel]

Nice :-)

[alexgarel]

BTW @stephanegigandet you should not fear moving file, git will be intelligent enough to follow changes through move if you use git mv.