1. We set the setting to false even though it's true by default
2. When true, an ORM warning appears at bootstrap because of how we register services to Hibernate ORM:

   2019-07-24 18:00:11,474 WARN [org.hib.ser.int.AbstractServiceRegistryImpl] (main) HHH000450: Encountered request for Service by non-primary service role [org.hibernate.search.mapper.orm.session.impl.HibernateOrmSearchSessionContextProvider -> org.hibernate.search.mapper.orm.mapping.impl.HibernateSearchContextService]; please update usage
   

3. Is it wise to set custom values for ORM settings in our test suite, effectively creating an environment that differs significantly from our user's?

Suggestions:

1. We should revisit how our services are registered in HibernateSearchContextServiceContributor. Avoid at all cost the use of keys that are interfaces that extend other interfaces also used as keys.
2. Maybe we should leave the allow_crawling setting to its default value.