[Dev] Fix ros_launch python issue

[lshmouse]

Description

[Dev] Fix ros_launch python issue

$ bazel run //experimental/ros2_example:ros_chatter 
INFO: Analyzed target //experimental/ros2_example:ros_chatter (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //experimental/ros2_example:ros_chatter up-to-date:
  bazel-bin/experimental/ros2_example/ros_chatter_launch.py
  bazel-bin/experimental/ros2_example/ros_chatter
INFO: Elapsed time: 0.229s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: bazel-bin/experimental/ros2_example/ros_chatter
Traceback (most recent call last):
  File "/home/qcraft/.cache/bazel/_bazel_qcraft/e1d25c724e0056022d92d7bdfe62b271/execroot/ai_playground/bazel-out/k8-fastbuild/bin/experimental/ros2_example/ros_chatter.runfiles/ai_playground/experimental/ros2_example/ros_chatter_launch.py", line 4, in <module>
    from ros2cli import cli
ImportError: cannot import name 'cli' from 'ros2cli' (/home/qcraft/.cache/bazel/_bazel_qcraft/e1d25c724e0056022d92d7bdfe62b271/execroot/ai_playground/bazel-out/k8-fastbuild/bin/experimental/ros2_example/ros_chatter.runfiles/ros2cli/__init__.py)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Unit Tests
• Manual Tests

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules