remove current repodata hacks

[isuruf]

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

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/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...

For recipe/meta.yaml:

• License exception is not an SPDX exception.

Documentation on acceptable licenses can be found here.

[beckermr]

I guess missed a bit my other PR. Lgtm!

[beckermr]

That was #70 in order to Xref the GitHub links.

[isuruf]

nvm, I was using an older commit

[h-vetinari]

So now that both this and #72 have been closed, what's the way forward for conda-forge/ctng-compilers-feedstock#147?

I maintain that #72 would be the proper way to do it (and would also rectify the situation that it's hard to tell where sysroot-with-crypt builds come from, as the existing ones just got the label added manually), but if you prefer to do it on top of v2.17 then I don't care. It should just be done one way or another (I guess a third option is something like #75 but for v2.17?).

(BTW, while looking at the branches I noticed that the tzdata changes have never been forward-ported from #66 to main)

[isuruf]

See #73