Add chafa and fastfetch

[pavelzw]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[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 (recipes/chafa, recipes/fastfetch) and found it was in an excellent condition.

[peterjc]

Doing two packages in one PR was probably a mistake - they don't depend on each other, do they?

[pavelzw]

Fastfetch depends on Chafa

[peterjc]

I missed that, but I don't think you'd be able to package fastfetch until after chafa is packaged. May is long enough ago that the failed run logs have gone, so we don't know how it failed.

Can you try cutting this down to just chafa? [I found this issue as I was interested in seeing chafa packaged, again as a dependency of something else]

[pavelzw]

Back then, chafa wasn't the issue but something else in fastfetch.

Conda-build is smart enough to first build chafa and then fastfetch in this ci. You might need to restart fastfetch's ci on feedstock creation though.
We could give chafa a try in a separate PR if you need it for an unrelated PR, though