test on 3.14

[graingert]

Changes

Fixes #.

Checklist

If this is a user-facing code change, like a bugfix or a new feature, please ensure that
you've fulfilled the following conditions (where applicable):

• You've added tests (in tests/) added which would fail without your patch
• You've updated the documentation (in docs/, in case of behavior changes or new
  features)
• You've added a new changelog entry (in docs/versionhistory.rst).

If this is a trivial change, like a typo fix or a code reformatting, then you can ignore
these instructions.

Updating the changelog

If there are no entries after the last release, use **UNRELEASED** as the version.
If, say, your patch fixes issue #123, the entry should look like this:

* Fix big bad boo-boo in task groups (#123 <https://github.com/agronholm/anyio/issues/123>_; PR by @yourgithubaccount)

If there's no issue linked, just link to your pull request instead by updating the
changelog after you've created the PR.

[agronholm]

Isn't this a wee bit too early? Given that the CI will show a failed result if the 3.14 job fails.

[graingert]

There's an a0 release - so we should probably see what happens

[agronholm]

As expected, uvloop breaks the test suite.

[graingert]

As expected, uvloop breaks the test suite.

well they're depending on a attribute that cpython deprecated but didn't warn on lookup

[graingert]

Lgtm