remove outputs that moved to ctng-compilers-feedstock

[h-vetinari]

Following conda-forge/ctng-compilers-feedstock#127, based on this comment. Probably we can close conda-forge/clang-compiler-activation-feedstock#118 after this PR.

Intentionally not incrementing the build number as nothing about the other outputs should change here.

[conda-forge-webservices]

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

It appears you are making a pull request from a branch in your feedstock and not a fork. This procedure will generate a separate build for each push to the branch and is thus not allowed. See our documentation for more details.

Please close this pull request and remake it from a fork of this feedstock.

Have a great day!

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

[beckermr]

Weird build failures for s390x but otherwise LGTM and thank you!

[conda-forge-webservices]

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

It appears you are making a pull request from a branch in your feedstock and not a fork. This procedure will generate a separate build for each push to the branch and is thus not allowed. See our documentation for more details.

Please close this pull request and remake it from a fork of this feedstock.

Have a great day!

[h-vetinari]

Weird build failures for s390x but otherwise LGTM and thank you!

Yeah, the s390x failures equally appeared in the most recent CI run on #98. Not sure what's happening there.

Also, sorry for creating a branch here - I'm guessing I must have made a C&P error while cloning, so that I ended up getting the wrong remote for origin. The good thing is that this didn't push new builds, because nothing else about the recipe changed - so I'll leave this for now, and fix my git remote setup in the meantime.

[beckermr]

Yep, all good! Let's merge!