[massive store] Use a slave specific table for relation insertion in the massive store * attribute a random id to the store * add a column containing this id in the cwmassive_initialized table * separate generic `master_init` which create the cwmassive_initialized table from rtype specific initialization which must be done in each slave now * delay removal of table indexes to `finish` * get back relations from each table on `finish` Similar work still has to be done for entities insertion - which will allow more cleanup to the constraints handling which is still rough for now. Related to #15538303

[MASTER]
load-plugins=cubicweb.pylintext
ignore=__pkginfo__

[MESSAGES CONTROL]
disable = too-many-ancestors,too-many-instance-attributes,too-many-public-methods,
      too-few-public-methods,too-many-arguments,import-error

[BASIC]
function-rgx = [a-z_][a-z0-9_]{2,35}$
good-names=w,_

[TYPECHECK]
generated-members=debug,info,notice,warning,error,critical,exception

[CLASSES]
exclude-protected=_cw,_cnx,
      # namedtuple public API.
      _asdict,_fields,_replace,_source,_make


[FORMAT]
max-line-length=100
max-module-lines=2000