ROS2 perception porting status

[fkromer]

@Kukanani

I would agree with the decision to avoid poor-performing packages to ROS2. In general, the large number of ROS1 packages can be daunting for someone who is just starting out, especially when it’s not immediately clear which of those packages are considered “best practice” or are even actively maintained. The ROS QA group should help alleviate this but I think the easiest way to make it clear is to simply not make older outdated packages available in ROS 2.

Probably it is not always just about performance but reliability in the architectural level as well: Functional Safety Design Patterns