Add recipe for icub-firmware-shared packages

[traversaro]

icub-firmware-shared is a set of C++ libraries shared among the firmware and the high level software used to control the iCub and ergoCub humanoid robots.

It is not particularly useful by itself, but I want to package it as it is a dependency of the icub-main C++ library used in the iCub and ergoCub humanoid robots, see #27672 .

The proposed recipe adds two different packages:

• libicub-firmware-shared: This is the package that is meant to be used if the package is consumed as a C/C++ library, and linked to a downstream project. To do so, the package contains a run_exports section. This package name contains the lib prefix as requested in Add recipe for libmatio-cpp #19764 (review) for C/C++ libraries.
• icub-firmware-shared: This is the package is an empty package that depends on libicub-firmware-shared and that is meant to simplify the transition from the robotology channel in which the icub-firmware-shared used to be called only icub-firmware-shared, without the lib prefix: https://anaconda.org/robotology/icub-firmware-shared .

The feedstock is named icub-firmware-shared to match the repo name and support different package outputs names in the future.

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.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[github-actions]

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/example-v1/recipe.yaml, recipes/icub-firmware-shared/meta.yaml, recipes/example/meta.yaml) and found some lint.

Here's what I've got...

For recipes/example-v1/recipe.yaml:

This is a v1 recipe and not yet lintable. We are working on it!

For recipes/example/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.

[github-actions]

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/icub-firmware-shared/meta.yaml) and found it was in an excellent condition.

[traversaro]

@conda-forge/help-c-cpp @conda-forge/staged-recipes the PR is ready for review, thanks!

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!