Update dagster-elasticsearch lockfile

[cmpadden]

Summary

• refresh dagster-elasticsearch uv.lock with latest compatible dependency versions

Testing

• uv lock --upgrade in libraries/dagster-elasticsearch

[cmpadden]

Pulled the failing check logs with gh. The test failed while talking to the Elasticsearch test server after the lockfile upgraded elasticsearch to 9.x. CI runs against an Elasticsearch 8 server, and elasticsearch-py does not support cross-major client/server combinations. Constrained elasticsearch to >=8.10,<9 and regenerated the lockfile. Also ran uv run ruff check and uv run ruff format --check locally for libraries/dagster-elasticsearch, then pushed the fix.

[cmpadden]

Revisited the earlier fix: instead of constraining the client to <9, this restores the intended loose client pin (elasticsearch>=8.10,<11) and keeps the lockfile on the latest 9.x client. The failed CI log showed a connection reset during the first integration test rather than an API incompatibility, while the fixture already defaults to an Elasticsearch 9.1.3 container. I updated the test fixture to wait for client.info() to succeed before yielding the test URL, so the suite actually exercises ES 9 and avoids racing the container startup. Ran uv run ruff check and uv run ruff format --check locally, then pushed the update.