Track packages that are released in ROS build farm but are/should be in conda-forge

The ROS Debian binary packages that are released via Bloom are essentially a distribution of software that builds on top of another distribution of software (the base Debian/Ubuntu repositories). This relation is similar to the one that in the conda world exists between conda-forge and bioconda channels, and in a sense is the same relation that we would like to create between conda-forge and robostack.

Over the time some packages that we not ROS-specific (i.e. they did not depend on the ROS communication middleware) were released with Bloom for several reasons. The major reason is that it was much faster and easier to get a package published via Bloom rather then by going through the actual Debian/Ubuntu packaging process, while in some other cases a package was indeed available in Debian/Ubuntu repos, but the version available in the repos was not recent enough, and it was not possible to update it due to Debian policies for updates in already released distros.

In the case of robostack, given that getting new packages in conda-forge is relatively easy and fast, and the same holds for updating the version of existing packages, I think it make sense to avoid to re-build packages that are or should be in conda-forge even if they are release in bloom/rosdistro, but rather we should have some systematic way to skip them and install the conda-forge version instead. I am not sure what is the proper way of doing so, but for the time being I opened this issue to track the occurrences of this pattern that I spot.

Just for ROS2, there are a few more in https://github.com/ros2/?q=vendor .

パッケージ表と、そこからリンクされている conda-forge、rosdistro、および関連する issue から始めます。どのパッケージが重複しているか、また vendor パッケージがファイルを追加するかどうかを比較します。完了条件は、Bloom を通じて再ビルドするのではなく conda-forge を使用すべきパッケージを特定するための、文書化された体系的な方法がプロジェクトに備わっていることです。