Add @xylar as a maintainer

[xylar]

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-linter]

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.

[xylar]

@conda-forge-admin, please rerender

[xylar]

@kalefranz and @mingwandroid, it doesn't look like the autobot is doing the trick here anymore. If you're willing to have me as a maintainer, I'd be willing to help get things working again.

I also need a build of 20.4.3 or 20.4.4 with python 3.10 to get the following PR in: conda-forge/poetry-feedstock#58. I'll create a temporary branch for that work, assuming you're okay with it.

[xylar]

I'm removing the automerge bot because I think that's causing trouble and dependencies aren't getting updated when they need to. In my view, the bot is only useful for packages that have fixed dependencies without constraints that could change with time. pip check will not notice that constraints are being violated unless an out-of-range version actually gets installed during testing, which is often not the case.

[xylar]

@conda-forge/core, this feedstock seems to have been left to the bots and neither of the maintainers has had any activity on GitHub for many months. Would one of you be willing to merge this so I can take over?

[xylar]

Thanks @isuruf!