Add recipe supabase pydantic

[kmbhm1]

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.

[kmbhm1]

@conda-forge/help-python

[kmbhm1]

I am willing to be listed here.

[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/supabase-pydantic/meta.yaml) and found it was in an excellent condition.

[synapticarbors]

One small change requested, but otherwise looks good.

[synapticarbors]

The license file looks like it's already included in the source distribution, so this can be removed.

[kmbhm1]

Thanks @synapticarbors. I have made the change; please re-review & thank you!