fix(deps): update dependency drupal/search_api_solr to v4.4.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
drupal/search_api_solr (source)	4.3.10 → 4.4.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock

Loading composer repositories with package information
Dependency drupal/search_api is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency drupal/core-composer-scaffold is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/core-recommended is locked to version 11.3.13 and an update of this package was not requested.
    - drupal/core-recommended 11.3.13 requires drupal/core 11.3.13 -> found drupal/core[11.3.13] but these were not loaded, because they are affected by security advisories ("SA-CORE-2026-012", "SA-CORE-2026-011", "SA-CORE-2026-010", "SA-CORE-2026-013"). Review the advisory details above for more information. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
  Problem 2
    - drupal/search_api is locked to version 1.41.0 and an update of this package was not requested.
    - drupal/search_api 1.41.0 requires drupal/core ^10.3 || ^11 -> found drupal/core[10.3.0-beta1, ..., 10.6.x-dev, 11.0.0-alpha1, ..., 11.x-dev] but these were not loaded, because they are affected by security advisories ("SA-CORE-2024-003", "SA-CORE-2024-004", "SA-CORE-2024-006", "SA-CORE-2024-007", "SA-CORE-2024-008", "SA-CORE-2025-001", "SA-CORE-2025-002", "SA-CORE-2025-003", "SA-CORE-2025-004", "SA-CORE-2025-007", "SA-CORE-2025-008", "SA-CORE-2025-005", "SA-CORE-2025-006", "SA-CORE-2026-001", "SA-CORE-2026-003", "SA-CORE-2026-002", "SA-CORE-2026-004", "SA-CORE-2026-007", "SA-CORE-2026-012", "SA-CORE-2026-008", "SA-CORE-2026-009", "SA-CORE-2026-005", "SA-CORE-2026-006", "SA-CORE-2026-011", "SA-CORE-2026-010", "SA-CORE-2026-013", "PKSA-h76q-q9b2-4kdc", "PKSA-787q-p7fn-mcw7", "PKSA-7kyj-yy4m-jzhv", "PKSA-j351-xv4b-pryh", "PKSA-d8tb-wwz2-ctxk", "PKSA-dh1f-zjm5-qg8y", "PKSA-bn52-vyzy-rmnm", "PKSA-xj83-g6g8-41vf", "PKSA-s1zc-gcfk-ddw5", "PKSA-ctyc-dmct-npkz", "PKSA-42zc-x5ss-z64p", "PKSA-s6zc-mws4-ngh4", "PKSA-xd2s-f2mt-7tf3", "PKSA-g51h-n1x3-mszr", "PKSA-jthw-vxjy-kxnx", "PKSA-ts55-c66h-g96n", "PKSA-yjvc-rnsz-8n3c", "PKSA-styk-3knc-d1bt"). Review the advisory details above for more information. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
  Problem 3
    - Root composer.json requires drupal/search_api_solr 4.4.0 -> satisfiable by drupal/search_api_solr[4.4.0].
    - drupal/search_api_solr 4.4.0 requires drupal/core ^11.3 -> found drupal/core[11.3.0-alpha1, ..., 11.x-dev] but these were not loaded, because they are affected by security advisories ("SA-CORE-2026-001", "SA-CORE-2026-003", "SA-CORE-2026-002", "SA-CORE-2026-004", "SA-CORE-2026-007", "SA-CORE-2026-012", "SA-CORE-2026-008", "SA-CORE-2026-009", "SA-CORE-2026-005", "SA-CORE-2026-006", "SA-CORE-2026-011", "SA-CORE-2026-010", "SA-CORE-2026-013", "PKSA-h76q-q9b2-4kdc", "PKSA-787q-p7fn-mcw7", "PKSA-7kyj-yy4m-jzhv", "PKSA-j351-xv4b-pryh"). Review the advisory details above for more information. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.
  Problem 4
    - drupal/lagoon_logs is locked to version 3.0.1 and an update of this package was not requested.
    - drupal/core 12.x-dev requires drupal/core-composer-scaffold 12.x-dev -> found drupal/core-composer-scaffold[dev-main, 12.x-dev (alias of dev-main)] but it conflicts with your root composer.json require (11.3.13).
    - drupal/lagoon_logs 3.0.1 requires drupal/core >=10 -> satisfiable by drupal/core[10.0.x-dev, ..., 10.6.x-dev, 11.0.x-dev, ..., 11.x-dev, 12.0.0-alpha1, 12.0.x-dev, 12.x-dev (alias of dev-main)].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.