Refresh the lock: pytest-asyncio 1.4.1, ty 0.0.92 (#169)

## Summary

Maintenance sweep, lock refresh only: pytest-asyncio 1.4.0 to 1.4.1 and
ty 0.0.91 to 0.0.92, both dev tools. The pyproject floors already admit
both, so no manifest change. No release: the wheel does not change.

Checked and found current: every runtime dependency, the GitHub Actions
pins, the uv version pinned in the workflows (0.13.5) and the
osv-scanner release (2.7.0). The holds were re-tested and still stand:
pympp 0.15 still exact-pins yarl and propcache and caps eth-abi below 6,
so the aiohttp floor and the `web3<8` constraint stay. The only
prereleases in the lock are the OpenTelemetry packages that have never
shipped a stable release.

## Type of change

- [ ] Bug fix (no breaking change)
- [ ] New feature (no breaking change)
- [ ] Breaking change (existing callers must update)
- [x] Docs, tests, or internal maintenance only

## Public API

none

## Test plan

Ran the CI gate set on Python 3.15 with the new lock: `uv sync --frozen
--all-extras --all-groups`, ruff check, ruff format --check, ty check on
the package and on the examples, vulture and pytest (1674 passed, 4
skipped). Every gate exited 0.

## Checklist

- [x] Tests cover the new behavior, and the suite passes locally
- [x] Lint, format, and type checks pass
- [x] Docs and README examples updated if the public surface changed (no
public change)
- [x] No secrets, credentials, or personal data in the diff or the tests

Author: vvillait88