Feature: disable eager loading in production and load the sections only if visited

[syphax-bouazzouni]

Context

One a user go to the ontology viewer of an ontology, e.g https://stageportal.lirmm.fr/ontologies/AGROVOC, it loads the current visited page and in the background fetch th remaining sections.
It is good if our API could support that amount of calls, but unfortunately it does overload the server with calls that are even possibly not even seen by the end users (e.g mappings section)
Now the following section are loaded in the background summary, classes, properties,instances,collections,schemes
And the following will be loaded only in visit mappings, notes, widgets, sparql

Changes

• Make the ontology viewer load the sections only if visited (6ab8354)
• Update the ontology viewer to lazy the section that are not data (de18fbd)

[Bilelkihal]

After deploying this to StagePortal, the UX is obviously worse.
I propose a compromise, we keep the eager loading only for classes/concepts and not for the other tabs.
@syphax-bouazzouni what do you think?