ESTransactionQueue batches all ES operations on postcommit.

Client cubes could override the default logic to add, log,
ditch… any other operation.

Indexer instances are the ones who know how to connect
to elasticsearch and which index should the query should
be executed on

As for ES "id" parameters, "doc_type" should be customizable,
there is no reason why es document type should match cw_etype

Default is to use 'eid' but one may want to use something
else (stable id, ark, etc.)

closes #17079908

For optimization sake, just make sure the original rset
fetches everyting or use complete=True but relying on
cw_attr_cache will cause very obscure bugs

closes #17079907

* get rid of CUSTOM_ATTRIBUTES. Replace it with IFullTextIndexSerializable adapter `custom_indexable_attributes`
  attribute;
* FullTextIndexSerializable.serialize method : default complete value is now True*


closes #17079905

otherwise the import just hand forever.

since it's a cube as package which are supported from there.

Besides from being a debug-only trace, it raises an error when
no actual document is indexed.

It's not used (and therefore not real-life-tested) anywhere
and current implementation is known to be partial and a bit
hard to maintain.

we should not crash if we try to delete an inexisting document

(closes #17071989)