NEW: Add recipe for libnvimgcodec

[carterbox]

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[bot]]

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/libnvimagecodec/meta.yaml) and found some lint.

Here's what I've got...

For recipes/libnvimagecodec/meta.yaml:

• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• The recipe must have a build/number section.
• The recipe license should not include the word "License".
• The about section contained an unexpected subsection name. feedstock_name is not a valid subsection name.

For recipes/libnvimagecodec/meta.yaml:

• Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [36, 93].
• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.