[massive store] Rework constraint/index handling The basic idea is to keep the primary constraint on entities.eid since it's heavily used in metadata insertions. Other option would have been to drop / recreate but its very costly on big database, and the index is used for insertion into the entities table itself, so it's not worth droping it at a first glance. Also, keeping it avoids to systematically drop all constraints which depends on it. We may thus now lazily drop constraints, only on insertion of some etype/rtype for the related table. Related to #15538359

[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