Fix initial DB seeding script

[lanseg]

Now an initial setup sql doesn't create orders, orders could be generated by the script from README.

The first run looks like this (default task will be changed in the further commits):

[marionb]

@lanseg This will only improve the ordere, but it will still mess up the sequence that is used for the generation of the ID of all the other tables like data_format, pricing and so on.
Now when we try to add/configure something in the shop this will end in an primary key error.

My idea was to create a dump with the whole data structure of a DB that is working and import it directly in the shop DB so that we have a working config with some test data. This would also avoid issues when running things twice.

alternatively you could update all the sequences.

[marionb]

The data you add will still cause the sequences in the DB and the rest of the data of the shop to be in an odd state. With this it will not be possible to add any new data in the shop going through the Django API.

If that is OK for you we can leave it but I think it would be better to have clean data.

Eventually we will have to clean up the DB if we want to test the whole chain with the geoshop FE and BE.