fix: trigger package rebuild on stale /pkgs volumes

packages_ready() gates package-init.sh on sentinel site-packages
directories. On an upgrade over an existing /pkgs volume, PIL,
markitdown, chdb and statsmodels are all already present, so the
check passed and the script exited before reaching the pip install.
The geospatial packages would never have landed on existing
deployments without a manual FORCE_REBUILD=true.

Add rasterio as a sentinel so stale volumes rebuild.

build-packages.sh needs no equivalent change: it clears
.package-installed and reinstalls unconditionally.

Author: danny-avila

docker/package-init.sh

@@ -92,6 +92,7 @@ packages_ready() {
     [ -d "/pkgs/python/${PYTHON_VERSION}/lib/python${PYTHON_SITE_VERSION}/site-packages/markitdown" ] &&
     [ -d "/pkgs/python/${PYTHON_VERSION}/lib/python${PYTHON_SITE_VERSION}/site-packages/chdb" ] &&
     [ -d "/pkgs/python/${PYTHON_VERSION}/lib/python${PYTHON_SITE_VERSION}/site-packages/statsmodels" ] &&
+    [ -d "/pkgs/python/${PYTHON_VERSION}/lib/python${PYTHON_SITE_VERSION}/site-packages/rasterio" ] &&
     [ -f "/pkgs/node/${NODE_VERSION}/.package-installed" ] &&
     js_packages_ready "/pkgs/node/${NODE_VERSION}" &&
     [ -f "/pkgs/bun/${BUN_VERSION}/.package-installed" ] &&