Migration base.0067_resourcebase_storetype broken

[etj]

Running migrations:
  Applying base.0067_resourcebase_storetype...Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/django/db/backends/utils.py", line 82, in _execute
    return self.cursor.execute(sql)
psycopg2.errors.UndefinedColumn: column "storeType" does not exist
LINE 4: FROM (select resourcebase_ptr_id,"storeType" from layers_lay...
                                         ^
HINT:  Perhaps you meant to reference the column "base_resourcebase.storetype".

Migration base.67

• has as dependency layers.0035_auto_20210525_0847
• adds field resourcebase.storetype
• SQL: copies storetype from layers.storetype

Migration layers.0036

• drops field storetype

Here the error is that in a dependency you can only specify the minimum version needed. Still, it's not said that you could have some more migration applied in the same app, so for sure the dep layers.0035 is satisfied, but also the layers.0036 has already been run, so the copy cannot be carried out.

The dependencies should assure that the field (or data) are where they are expected, so we may want to add a dependency toward the migrations that copies the data before removing the field.

We need to change:

• layers.0036
  • ensure the data have been copied, so add a dependency to base.0067_resourcebase_storetype
• base.0067
  • remove the useless dependency to layers.0035

Please also note that an analogous change is needed for documents.

Currently base.0067 is dependent on documents.0032_remove_document_doc_file, which is useless per se, and the author prolly wanted to avoid the execution of documents.0033_remove_document_doc_type which removes the field used in the copy procedures.
Anyway documents.0033_remove_document_doc_type has a dep on base.0067, so it makes sure the data are copied before removing the field.

• base.0067
  • remove the useless dependency to documents.0032