Aligned requirements with upstream 2.6.1

[timostrunk]

Upstream pyproject.toml changed a lot:
https://github.com/rthalley/dnspython/blob/main/pyproject.toml
As far as I understand nothing is required anymore. I kept the sniffio dependency, because I don't want to break current users and sniffio is used in the asyncio check.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[timostrunk]

@conda-forge-admin, please rerender

[synapticarbors]

@timostrunk -- good catch. I guess the grayskull update doesn't catch run_constrained requirements? I think this looks good, but will wait for the other co-maintainers to chime in before merging.

[xylar]

I think we should remote bot automerge to prevent this kind of thing happening.

[xylar]

https://github.com/timostrunk/dnspython-feedstock/blob/fix_requirements/conda-forge.yml#L3

[xylar]

My guess is that the grayskull bot update failed because grayskull is still struggling with certain pyproject.toml syntax (lists of dependencies with different constraints conda/grayskull#463).

[synapticarbors]

@timostrunk -- would you remove the automerge from the config shown in #18 (comment)? Then I think we should be good to merge this PR.

[timostrunk]

Will do

[timostrunk]

@conda-forge-admin, please rerender

[timostrunk]

Automerge is removed and I rerendered afterwards

[xylar]

Thanks @timostrunk!