IBX-12271: Implemented Solr 10 support

[barw4]

🎫 Issue	IBX-12271

Description:

Scope decision: Solr 8/9 support is dropped on 6.0 — Solr 10 only. .github/init_solr.sh deliberately keeps its 7.7/8/9 provisioning branches (other packages' CI uses it), and the legacy schema files (schema.xml, custom-fields-types.xml) stay because that script's pre-9 path copies them.

Changes

• language-fieldtypes.xml (default + solr.languages/en): SynonymFilterFactory → SynonymGraphFilterFactory — proactive: still works in 10.0 but deprecated; its managed variant was already removed in 10.0 (ref). Query-time only, no reindex; fixes multi-word synonym matching.
• .github/init_solr.sh: accept 10.x; --user-managed start, --solr-home (Solr 10 repurposed -s for --solr-url), bin/solr create, bin/solr zk upconfig instead of removed zkcli.sh; maxShardsPerNode only sent to pre-9 (ref, 10.0.0 CHANGES: SOLR-16893, SOLR-17467, SOLR-14115). Default version 9.8.1 → 9.10.1; 7.7/8.x/9.x invocations unchanged.
• bin/generate-solr-config.sh: version-aware download URL (was broken for 9.x — still pointed at dist/lucene/solr), solr.xml/allowUrls handling extended to 10.x, defaults → 10.0.0 and .platform/configsets/solr10/conf. Non-10.x versions print a warning but still work (no hard error — init_solr.sh and ibexa/core's docker/solr image call this script for older versions). All four solrconfig.xml sed patches verified against real 9.10.0/10.0.0 _default files.
• Bugfix (both scripts): the autoSoftCommit.maxTime patch matched only the pre-9 upstream default (-1; it's 3000 since 9.x) and was silently no-oping — now matches any value.
• CI: matrix reduced to 10.0.0 × 4 core setups; actions/setup-java with Temurin 21 — Solr 10 requires Java 21 (ref).
• Configuration::SOLR_DEFAULT_VERSION → 10.0.0; MapLocationDistanceRange version branching removed (modern LatLonPointSpatialField path only, $solrVersion ctor arg + %ibexa.solr.version% wiring dropped; the version config node stays for BC); new testVersion provider; README supported-versions/Java note; 7.7-era @see links refreshed.
• Handler::deleteLocation(): the "has an additional Location" classifier used the Lucene regex complement operator ~, removed from default syntax flags in Lucene 10 (LUCENE-10010) — on Solr 10 it silently matched nothing, deleting surviving content from the index (SearchEngineIndexingTest::testDeleteLocation). Replaced with a block-join child query (_query_:"{!parent …}(+document_type_id:location -path_string_id:…)") — Locations are indexed as child documents, so the classifier is a plain boolean NOT; two-query delete/reindex flow unchanged. The reindex loop now also guards load() with NotFoundException, as the persistence cache can serve a stale ContentInfo right after a deletion (testDeleteContent on CI).

For QA:

Documentation:

[konradoboza]

Nice work! Please make sure to add Doc needed label.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud