After discussions on HSEARCH-2216, we agreed:

• not to change the Elasticsearch type name to a non qualified name by default (Sanne's lead hammer)
• offer another strategy contract: TypeNamingStrategy which allow users to provide a different name for the Elasticsearch type (than the FQCN).

The default TypeNamingStrategy would provide the FQCN as the type name.

Questions remaining,

• should we store the classname in the type structure _meta? We could offer a bidirectional TypeNamingStrategy and not store anything
• if we decide to store, should we only store it when the TypeNamingStrategy deviates from the default one? how to recognized a true FQCN from a modified one?