feat: add atlas-schema into conda-forge

[kratsg]

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

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/atlas-schema/meta.yaml) and found some lint.

Here's what I've got...

For recipes/atlas-schema/meta.yaml:

• ❌ The home item is expected in the about section.

[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 (recipes/atlas-schema/meta.yaml) and found it was in an excellent condition.

[kratsg]

@conda-forge/help-python, ready for review!

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/atlas-schema/meta.yaml) and found some lint.

Here's what I've got...

For recipes/atlas-schema/meta.yaml:

• ❌ noarch packages can't have skips with selectors. If the selectors are necessary, please remove noarch: python.

[matthewfeickert]

@kratsg you can keep it noarch.

[kratsg]

@kratsg you can keep it noarch.

done

[matthewfeickert]

@kratsg, btw, for future testing the conda-forge team made it even easier now to do local builds before opening up an "Add project" PR by adding a pixi project config. So you now can just do

staged-recipes/README.md

Lines 49 to 51 in 566507c

	* `pixi run build-linux`: will launch a Docker container, provision all the necessary tools and build your recipe for Linux.
	* `pixi run build-osx`: will provision a conda environment with the necessary tools to build your recipe for macOS. This involves fetching and caching the necessary Apple SDKs.
	* `pixi run build-win`: will provision a conda environment with the necessary tools to build your recipe for Windows.

for the next project you add to test everything before pushing. 🚀

[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 (recipes/atlas-schema/meta.yaml) and found it was in an excellent condition.

[kratsg]

@ocefpaf - all changes commited/made.

[matthewfeickert]

Thanks very much for all your help and patience, @ocefpaf!