Deprecated.
The system should be automatically able to detect collections that require multitenant behavior. An exception
to this is a ManyToMany collection using a join table. In such a situation, you should consider modelling the join table
as an entity itself and convert the collection to a OneToMany using that new "join table" entity.
Used to mark collections for multi-tenancy when the commercial multi-tenant module is loaded. Please note, multi-tenant
collections are NOT eligible for level 2 cache, which results in a query to the database every time the collection is lazy initialized.
This can result in production performance degradation depending on how frequently the collection is utilized. It is
for this reason that we recommend utilizing a custom service or service extension that explicitly creates a query
for the collection entity members based on the parent entity. See the multi-tenant module documentation for more
information.