Relations dictionary to order tables

[frederik5480]

We might be able to make a default implementation like this that takes a dictionary and orders things properly, but for now I have put it as a provider specific implementation to get some thoughts.

In general I would like some feedback on this sort of way of doing it - it requires changes in the BaseProvider (hence this would bump the dependencies to 10.4.0 and should not be merged till we actually make a release with those new additions)

I do realize that if we have a dependency that says table C has a foreign key to B and B has a foreign key to A, then A should always be first, but in this implementation that is not considered as there is no relations that goes like that, only 1 step down.

[DWDBE]

Looks good, but there are still some tables that are missed:

{ "EcomVariantsOptions", [ "EcomLanguages" ]},
{ "EcomPrices", [ "EcomLanguages" ]},

Also we need to stick to the order of how it was before so EcomVariantGroups needs to be first/before the EcomProducts table as there are virtual columns in the EcomProducts/(and some other tables) that are used and trying to perform the search for the ids in the DataTables that are filled during the import to have correct references found by name/etc