dep!: Set project node version to ^22.22.2 || ^24.15.0 || >=26.0.0

[maxreichmann]

This bumps the project's node engine requirements:
--> from ^22.20.0 || >=24.0.0
--> to ^22.22.2 || ^24.15.0 || >=26.0.0

Alignes with requirements used in @npmcli packages and npm 12.
Solves engine conflict in #1494.
Adds new node version (26) to CI test matrix.
Updates documentation.

[matz3]

Two remarks:

• Should we also bump the v24 requirement, as we now require a v22 version from March 2026, but still allow the initial v24 release from May 2025? To me this does not fit right now, and the v22 version might contain more features (back-ports), than the v24. Also, looking at #1494 (comment) it was stated that the @npmcli/config package needs ^22.22.2 || ^24.15.0. But actually it needs ^22.22.2 || ^24.15.0 || >=26.0.0 (based on version 11.0.1)
• Should we rather declare this as a breaking change, to make our requirement changes clear in the next alpha release notes?

[matz3]

Third remark:

Do you know why the CI does not fail? I would have expected that the check via #1360 catches that.
EDIT: Nevermind. The dependency doesn't get updated in this PR, so it would only fail there. All good here, no CI issue.

[flovogt]

Should we also bump the v24 requirement, as we now require a v22 version from March 2026, but still allow the initial v24 release from May 2025? To me this does not fit right now, and the v22 version might contain more features (back-ports), than the v24. Also, looking at #1494 (comment) it was stated that the @npmcli/config package needs ^22.22.2 || ^24.15.0. But actually it needs ^22.22.2 || ^24.15.0 || >=26.0.0 (based on version 11.0.1)

I agree. Let set the version to ^22.22.2 || ^24.15.0 || >=26.0.0 for now

Should we rather declare this as a breaking change, to make our requirement changes clear in the next alpha release notes?

As we are still in the alpha phase every new release might be breaking. As we edit the changelog for initial v5 later anyway, I guess its fine to mark this as breaking

[matz3]

As we are still in the alpha phase every new release might be breaking. As we edit the changelog for initial v5 later anyway, I guess its fine to mark this as breaking

Yes, we need to state the breaking changes compared to v4 in the final v5.0.0 release. I agree that we should add this breaking change to inform front-runners who want to test our pre-releases.

EDIT: Sorry, I first misunderstood your point.

[maxreichmann]

Update:

• Set node version requirements to: ^22.22.2 || ^24.15.0 || >=26.0.0
• Add node 26 to CI test matrix (@UI5/ui5-team-cor-fnd ?)