Deps: Bump to Eclipse Sisu 1.1.0

[cstamas]

Release notes:
https://github.com/eclipse-sisu/sisu-project/releases/tag/releases%2F1.1.0

Fixes #12522

[gnodet]

CI Failure Analysis

Same failure as #12551 — all 18 downstream checks (full-build + integration-tests) fail with:

[INFO] Resolving Mimir daemon version 0.12.0
[WARNING] Failed to resolve daemon: Unknown NameMapper name: 'file-gaecv', known ones: []
[ERROR] Error enabling Mimir: java.io.IOException: Mimir daemon JAR not found

initial-build passes (Maven 4.0.0-rc-5 wrapper uses Sisu 1.0.1). The downstream jobs run the newly-built Maven with Sisu 1.1.0, where the new JSR330 bean filtering (sisu-project#266) hides all NameMapper implementations from the Mimir extension realm (known ones: []).

See analysis on #12551 for details.

[gnodet]

Update: TCCL + Realm Visibility Root Cause

Posted a detailed analysis on #12551 — the issue is the interaction between DefaultMaven.callListeners() setting TCCL to the extension realm (line 376), and Sisu 1.1.0's new FilteredBeans in DefaultBeanLocator.locate() using RealmManager.contextRealm() (which walks the TCCL) to determine visibility. Mimir's realm can't see plexus.core's NameMapper beans under the new filtering.

See #12551 comment for full details and fix directions.

[gnodet]

Closing in favor of #12554 (master) and #12556 (4.0.x), which fix the root cause properly.

The original approach of just bumping Sisu to 1.1.0 exposed a realm visibility issue: extension realms (parent=plexus.core) couldn't see beans sourced from the maven.ext container realm through Sisu 1.1.0's new jsr330ComponentVisibilityFollowsPlexusVisibility filtering. The fix adds a reverse realm import (realm.importFrom(extRealm, extRealm.getId())) so that maven.ext is reachable in Sisu's visibility BFS traversal from extension realms — working with the filtering feature, not against it.