pro document detailed view: optimize item loading

[PascalRepond]

How it works

When loading holdings/items in the document detailed view, many ES queries are used to check the permissions for the delete buttons beacause the holdings' reasons_not_to_delete must check that all items can be deleted. For holdings with many items, this can lead to thousands of ES queries on page loading. Some of these queries are useless or redundant and could be better optimized.

Example for a document with many items: https://bib.rero.ch/professional/records/documents/detail/460668

Improvement suggestion

1. Add a parameter to the links_to_me method allowing to not take into account the links from local_fields and use it in reasons_not_to_delete for documents, holdings and items.
2. When calculating permissions for a holding/document, do not call reasons_not_to_delete for every item but instead build 3 ES queries (loans, fees, collections) for all items?
3. When calculating availability in the brief views, do not call an ES query for each holding and item but instead build a query for all items/holdings at once if possible