[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

     1

### Requirements for tests in various cubicweb/**/test directories. ###

     2

     3

## shared by several test folders

     4

cubicweb-card

     5

docutils

     6

Twisted < 16.0.0

     7

webtest

     8

     9

## cubicweb/test

    10

Pygments

    11

mock

    12

#fyzz XXX pip install fails

    13

cubicweb-file

    14

cubicweb-localperms

    15

cubicweb-tag

    16

    17

## cubicweb/devtools/test

    18

flake8

    19

    20

## cubicweb/hooks/test

    21

psycopg2

    22

    23

## cubicweb/pyramid/test

    24

pyramid >= 1.5.0

    25

waitress >= 0.8.9

    26

wsgicors >= 0.3

    27

pyramid_multiauth

    28

    29

## cubicweb/sobject/test

    30

cubicweb-comment