* Refactor READ ONLY mode in Context and adjust hibernate settings accordingly
* Set Context in READ-ONLY mode when retrieving community lists
* Fix Hibernate EHCache configuration + fix some Hibernate warnings
* Cache authorized actions and group membership when Context is in READ-ONLY mode
* Set default Context mode
* Let ConfigurableBrowse use a READ-ONLY context
* Add 2nd level cache support for Site and EPerson DSpaceObjects
* Added 2nd level caching for Community and Collection
* Fix tests and license checks
* Cache collection and community queries
* Small refactorings + backwards compatibility
* Set Context to READ-ONLY for JSPUI submissions and 'select collection' step
* OAI improvements part 1
* OAI indexing improvements part 1
* OAI indexing improvements part 2
* DS-3552: Only uncache resource policies in AuthorizeService when in read-only
* DS-3552: Additional comment on caching handles
* DS-3552: Fix cache leakage in SolrServiceResourceRestrictionPlugin
* DS-3552: Clear the read-only cache when switching Context modes
* DS-3552: Correct Group 2nd level cache size
* DS-3552: Always clear the cache, except when going from READ_ONLY to READ_ONLY
dspace-rdf was developed as standalone module. At the end of the
development most of it was moved to be included into dspace-api. Instead
of using Spring it used its own class that instantiated all necessary
classes. This PR solves the problem described in DS-3190 by refactoring
org.dspace.rdf to adapt patterns used in DSpace 6. It introduces
[dspace]/config/spring/api/rdf.xml to configure spring to instantiate
all necessary classes. org.dspace.rdf.RDFConfiguration was removed
completely, the configuration keys are centralised in
org.dspace.rdf.RDFUtil. Instead of org.dspace.rdf.RDFConfiguration and
DSpace's old ConfigurationManager the new ConfigurationService is now
used everywhere. Configuration properties shouldn't be hold in variables
anymore so that RDF profits from the new autoreload function from
DS-2654.
Originally, one sortOrder configured in the discovery.xml spring file would be used.
This had an impact on both the sidebar and view more pages
This commit splits this sortOrder to make it possible to have different sortOrder for the view more page and sidebar facet
This was an improvement based on the following Jira ticket
https://jira.duraspace.org/browse/DS-2635
