feat: add smoke test inputs to CI workflow

[DeepDiver1975]

Summary

• Passes smoke test inputs to the reusable docker-build.yml workflow (requires feat: add optional smoke test step to docker-build workflow ubuntu#263 merged ✅ and fix: handle curl network errors in smoke test polling loop ubuntu#265 merged first)
• Starts the built image on port 8080 with SQLite3 and polls /status.php for HTTP 200
• Asserts .versionstring in the response JSON matches the matrix version for all stable releases
• 11.0.0-prealpha skips version assertion (smoke-version-jq: "") since the daily tarball version is unpredictable

Behaviour per matrix entry

Version	HTTP 200 check	Version assertion
10.16.2	yes	.versionstring == 10.16.2
10.16.1	yes	.versionstring == 10.16.1
10.15.3	yes	.versionstring == 10.15.3
11.0.0-prealpha	yes	skipped

Why the smoke test was failing

The smoke-test step runs under bash -e -o pipefail. Docker's userland proxy binds the host port and accepts TCP connections immediately, before Apache inside the container is ready. ownCloud's first-run SQLite init takes ~60–90 s, so the very first curl attempt receives a connection reset (exit code 56 = CURLE_RECV_ERROR). With set -e, that aborts the script immediately — the EXIT trap then calls docker stop explaining the characteristic 10 s gap before the CI error. Fixed in owncloud-docker/ubuntu#265 by adding || STATUS="000" so curl network errors continue the polling loop rather than aborting.

🤖 Generated with Claude Code