CI: add an arcadedb-tag input to pin the ArcadeDB image (release builds use latest) #3

Both workflows always build from arcadedata/arcadedb:latest. download-jars pulls that tag and works out the version from the engine jar. Neither workflow_dispatch nor workflow_call has an input to choose a different image tag; build-version only changes the PEP 440 version string.

The problem: a release build has no way to target 26.11.1 or an RC. It would get whatever latest is at that moment, which is the current snapshot.

Proposed fix: add an arcadedb-tag input (default latest) to both workflows. download-jars would pull arcadedata/arcadedb:<tag>, and the job outputs would carry it through. scripts/build.sh already reads ARCADEDB_TAG.

Found in the final review of the move from ArcadeData/arcadedb (#1).

🤖 Generated with Claude Code