Revert S3 Support

[akrherz]

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.

Reverts S3 support added in #180 in hopes of helping #182 until a permanent fix can be found.

[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.

[akrherz]

@conda-forge-admin please rerender

[xylar]

@akrherz, thanks for doing this. I think we need to revert this for now so we can make headway with migrations more broadly on conda-forge. Obviously, we can revisit this as soon as there's a fix, as folks are exploring in #182

[akrherz]

Anybody willing to smash the green button here, so we can get migrations moving again?

[kmuehlbauer]

@akherz It looks like we have consensus here. Thanks for doing the hard work.

[akrherz]

Again, a total FWIW and likely something I have screwed up, but I have found this updated build no longer does flakey things (segfaults, etc) on github actions with my own repos. I'll be sure to watch when S3 support comes back in the future and if flakey things happen then too or not.

[xylar]

Sounds promising! Let's hope when it comes back, it's more stable.