For all the files that uses the structWSF-PHP-API, we make sure that they uses the DrupalQueryExtension() to use the
special Drupal querying specificities when it uses the structWSF-PHP-API.

[#HPP-915] Refactored code to minimize requests per handler and to remove extra API query for total count

Reverted the last commit; we may want to add a configuration option for this in the future, but for now, it would mean
that for each result, and for each call of the view, it would write the cache which would be an unnecessary overhead
for most usecases.

Each time structViews does send a query to the Search endpoint, it gets the full description of the records
returned by the endpoint. What structViews then do, is to create the entities of type "resource_type" using
that information that come from the Search endpoint.

The additional step we are doing here, is to add the entity that get created into Drupal's entities cache.
That way, each time this entity will be loaded using entity_load() elsewhere in drupal, it will come from the
cache instead of sending a query to the CRUD: Read endpoint.

The core Resultset.php properties "description" and "prefURL" were missing into the Entities mapping. The end result
was that these properties were not mapped into the Drupal Resource Type entities that were created by structViews and
structEntities.