Relax asyncer==0.0.8 exact pin to a range

## Summary `dspy` pins `asyncer==0.0.8` exactly. Exact-version pins in a widely-consumed library create transitive resolution conflicts for any downstream project that pulls in a newer `asyncer` (directly or via another dependency). ## Impact Downstream Dependabot upgrades for packages sharing the anyio/asyncer dependency chain get blocked until this pin is relaxed. We are hitting this on two open Dependabot PRs in our monorepo. ## Proposed fix Change `asyncer==0.0.8` → `asyncer>=0.0.8,<1.0` (or `<0.1` if the maintainers want to stay conservative given asyncer's pre-1.0 cadence). `asyncer` 0.0.9+ is API-compatible with 0.0.8 for the surface dspy uses (primarily `asyncify`/`syncify` wrappers). ## Evidence - asyncer changelog: https://asyncer.tiangolo.com/release-notes/ - dspy's usage is narrow and unaffected by post-0.0.8 changes ## Context Filed from the LexAggregator project. Happy to send a PR if the direction is confirmed.