Description updates from solrj8.11.1 to 8.11.2 sets match version in solrconfig from 8.9.0 to 8.11.2

Description Solr Index build creates a lot of "info" logslike: Solr API request ListAliases was successful

Description When deleting one or more (per batch) products in the backoffice (master or channel) then

Description With #86470 a retry for the restore command was introduced. But if the restore fails

Description With the parallel backup and restore introduced in #87503 the initial replication fails frequently

Description ICM replication process does fail on BackupAndRestoreSolrCloudIndexesDecorator.onPostReplicationHook

Description Replication from search indexes especially the Backup and the Restore does consume lot of

Description Optionally allow the Solr replication to rebuild the inconsistent search indexes instead

Description If a replication collection exist in the live system but no ConfigSet Alias for it, the old

Actual Behavior On occasion the collection(s) that are created during an initial build on the live side

Description During ICM runtime the Solr Cloud adapter code throws in a lot of "Closing JDBC connection

Description Can't find declaration of instance 'intershop.EnterpriseBackoffice.Cartridges' for adding

Description The 'index locked' message in the search index list introduced with #57500  does not appear

Description Improves performance of indexing documents into Solr by send the document (SolrInputDocument)

Description When using an object suggest index then in the suggestion box the product count does include

Description When there is a category path that never ends up at the root with parent = null the So

Description After a successful index build the alias is switched to the newly built collection. Afterwards

Description When deleting a search index in back office of a channel the index is deleted. But at the

Description Define  a keyword '%' with synonym 'percent' Delete the keyword Error: [2022-11-24 14:55:14

Description Importing a new synonym file that changes a lot of synonyms can cause a internal server error