release: prepare Base 1.10.0 with latest ecosystem pins

[codeforester]

Summary

Prepare the Base 1.10.0 release line from the latest main candidate:

• update VERSION to 1.10.0 and advance DEVELOPMENT_VERSION to 1.11.0;
• align Base source-checkout, demo E2E, lint, setup, and reusable-check workflows with published base-cli 0.5.1 (aa20cfe89bc3568ff19f8cc1414372feadb00fd4) and base-bash-libs 2.2.2 (1333c0e7e4c3004663cda635e04965cb9d76511d);
• update the ecosystem BOM workflow defaults and downstream dependency record;
• refresh current release documentation, provider diagnostics, and release identity metadata.

This is the Base-side handoff needed before the base-demo provider alignment can become a stable release. The demo alignment PR #352 has already passed its advisory Base 1.10 scenario lane; its stable Base 1.9 source-provider lane correctly exposed that base-cli 0.5.1 requires the manifest support now present in this Base 1.10 line.

Issues

Refs #2482
Refs #2291

Validation

• git diff --check
• targeted workflow/provider and docs tests: 26 passed
• bin/base-test: 1786 tests collected; the only failure was the release-prep invariant after VERSION advanced while DEVELOPMENT_VERSION still matched, then the invariant passed after advancing DEVELOPMENT_VERSION to 1.11.0.

After merge, the release owner must run the exact two-platform Ecosystem Release BOM with the final merge SHA, the published component refs above, and the selected immutable base-demo release. The BOM—not this PR—remains the publication proof.