[github-actions]

Weekly re-resolve of A2UI5_PIN against abap2UI5 main (e4d89a69c7fe7f6c2652ef7852a1eb012e98714d) —
what node-setup, the Pages build and the e2e smoke run against.
The abaplint configs resolve main directly (unpinned), and the
nightly e2e keeps testing main tip as the canary.

The verdict at the new pin

The strict e2e smoke FAILED at the new pin. Read this PR as the report of a breaking framework change — here is the change, and below is what it broke — not as a routine bump. Do not merge it to clear the badge: either the ports below get their fix in this same PR, or the pin waits for an upstream fix and this PR is closed.

Run: https://github.com/abap2UI5/samples-controls/actions/runs/39404751001

e2e-smoke: 622 port(s), backend from /home/runner/work/samples-controls/samples-controls/.abap2UI5 on http://localhost:3000
FAIL  overview  boot: the control never appeared — tried 0 overflow popover(s)
e2e-smoke: 628 app(s), 1 failing.

Every FAIL line is a port whose live wire broke against the new
framework commit — or a harness effect, see .claude/skills/e2e-debugging.