Add ros2 package names to the Rolling page

[mini-1235]

Summary

• include canonical ros2-* artifacts on the Rolling package page while retaining legacy ros-rolling-* compatibility packages
• store and display exact Conda artifact names without changing Humble, Jazzy, Kilted, or Lyrical naming
• recommend ros2-* in Rolling installation examples

Validation

• pixi run lint
• pixi run build-docs
• pixi run python scripts/compare_pkg_completeness.py rolling https://prefix.dev/robostack-rolling
• verified generated non-Rolling pages contain no ros2-* package instructions
• git diff --check

[mini-1235]

I have only applied this pattern to Rolling for now. I assume we don't want to apply it to the other distros yet.

[Hofer-Julian]

Thanks, I pushed a few fixes

[traversaro]

It seems that now on older mutexes with ros-rolling-<pgk> names, the percentage of packages available is 0%. Perhaps we can split ros2-<pkg> or ros-rolling-<pkg> not at the distro level, but on distro + mutex number?

fyi @Hofer-Julian

[Hofer-Julian]

It seems that now on older mutexes with ros-rolling-<pgk> names, the percentage of packages available is 0%. Perhaps we can split ros2-<pkg> or ros-rolling-<pkg> not at the distro level, but on distro + mutex number?

fyi @Hofer-Julian

Good one, let me fix that