Adding faster-coco-eval

[MiXaiLL76]

Hello, I suggest to include the fast validation library "faster-coco-eval" for validating coco & lvis datasets.

The guys from lightning.ai have been using it for a long time as an alternative backend for validation, instead of the dying pycocotools.

https://lightning.ai/docs/torchmetrics/stable/detection/mean_average_precision.html

For quick comparison, here is a table from the end of this document:

ultralytics eval compare considering data loading

lib	model	time	profit
faster-coco-eval	bbox	7.34	4.5x
pycocotools	bbox	34.35	1x
----	-----	----	------
faster-coco-eval	bbox+segm	26.51	3.2x
pycocotools	bbox+segm	86.79	1x
----	-----	----	------
faster-coco-eval	bbox+keypoints	4.45	2,2x
pycocotools	bbox+keypoints	10.17	1x

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

Here's what I've got...

For recipes/faster-coco-eval/meta.yaml:

• ❌ This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12467379037. Examine the logs at this URL for more detail.}

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

[MiXaiLL76]

@conda-forge-admin, please ping conda-forge/help-python-c

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/help-python-c and so here I am doing that.