Default deploy installs eoapi-cdk 10.3.0, whose STAC runtime fails to import (`No module named 'stac_fastapi.extensions.core.fields'`)

Deploying eoapi-template from a fresh clone produced a STAC API that returned 500 Internal Server Error on every request. The cause seemed to be dependency resolution: `pyproject.toml` specifies `eoapi-cdk>=10.3.0,<12`, and a fresh `uv sync` resolves to the lower bound, 10.3.0. The STAC API runtime bundled by eoapi-cdk 10.3.0 raises an `ImportModuleError` at Lambda handler import. Upgrading eoapi-cdk to 11.6.0 resolved it for me.

**Environment:**

- Fresh clone of eoapi-template, deployed to AWS (us-west-2)
- uv sync resolved eoapi-cdk==10.3.0 (confirmed in uv.lock)
- Python 3.14.2, Node v24.13.0, deployed via `npx cdk deploy --all`

**What happened:**

Once deployed, I attempted to hit the STAC API endpoint:

Looking in the CloudWatch logs I noticed:

Forcing eoapi-cdk to the latest version resolved it. Upon redeploying, I was able to hit the endpoint:

Start with the eoapi-cdk constraint in pyproject.toml and the resolved version in uv.lock; run uv sync to confirm the dependency resolution. Update the dependency so a fresh deploy no longer selects 10.3.0, then run npx cdk deploy --all and verify that the STAC API endpoint responds without the Lambda import error.

Written by the indexing model from the issue text.