update to 0.6.6

[bollwyvl]

Checklist

• Used a 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.

• unblocks dagit v0.6.6 dagit-feedstock#2

It appears the upstream filename changed.

Also, while looking over the repos, it looks like dag(ster|git)* are simultaneously released with the same version. Perhaps it makes sense to:

• move them all into one feedtock (dagster?)
• keep triggering the bot off the main dagster pypi tarball, as they make tags-per-push
• do all the builds from source.

It's a big source tarball (they check in their yarn packages) but it should be much easier to keep everything consistent.

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

[bollwyvl]

@conda-forge-admin, please rerender

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-webservice.

I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance. You can also try re-rendering locally.

[bollwyvl]

(re-rendering locally did nothing)