Reorganize the autoware.universe/common packages

[youtalk]

Despite the name "common," the autoware.universe/common directory contains many packages that are only used by specific modules.

Move these packages to specific directories to clarify dependencies and relationships. This is a preparatory step for multi-containerization.

Packages in autoware.universe/common:

• autoware_ad_api_specs
  • refactor(autoware_ad_api_specs): prefix package and namespace with autoware autoware.universe#9250
• autoware_auto_common
• autoware_grid_map_utils
  • refactor(autoware_grid_map_utils): prefix folder structure with autoware/ autoware.universe#9170
• autoware_mission_details_overlay_rviz_plugin
• autoware_motion_utils
• autoware_overlay_rviz_plugin
• autoware_path_distance_calculator
• autoware_perception_rviz_plugin
• autoware_point_types
  • refactor(autoware_point_types): prefix namespace with autoware::point_types autoware.universe#9169
• autoware_test_utils
• autoware_testing
• autoware_universe_utils
• bag_time_manager_rviz_plugin
• component_interface_specs
  • refactor(component_interface_specs): prefix package and namespace with autoware autoware.universe#9094
• component_interface_tools
  • refactor(component_interface_tools): prefix package and namespace with autoware autoware.universe#9093
• component_interface_utils
  • refactor(component_interface_utils): prefix package and namespace with autoware autoware.universe#9092
• cuda_utils
  • refactor(cuda_utils): prefix package and namespace with autoware autoware.universe#9171
• fake_test_node
  • refactor(fake_test_node): prefix package and namespace with autoware autoware.universe#9249
• geography_utils
  • refactor(geography_utils): prefix package and namespace with autoware autoware.universe#7790
• global_parameter_loader
• glog_component
• goal_distance_calculator
  • refactor(goal_distance_calculator): prefix package and namespace with autoware autoware.universe#9172
• interpolation
  • refactor(autoware_interpolation): prefix package and namespace with autoware autoware.universe#8088
• kalman_filter
  • refactor(kalman_filter): prefix package and namespace with autoware autoware.universe#7787
• object_recognition_utils
  • refactor(polar_grid): add autoware prefix to polar_grid autoware.universe#8945
• osqp_interface
  • refactor(osqp_interface): added autoware prefix to osqp_interface autoware.universe#8958
• perception_utils
• polar_grid
  • refactor(polar_grid): add autoware prefix to polar_grid autoware.universe#8945
• qp_interface
  • refactor(qp_interface): prefix package and namespace with autoware autoware.universe#9236
• signal_processing
  • refactor(signal_processing): prefix package and namespace with autoware autoware.universe#8541
• tensorrt_common
• tier4_adapi_rviz_plugin
• tier4_api_utils
• tier4_camera_view_rviz_plugin
• tier4_datetime_rviz_plugin
• tier4_localization_rviz_plugin
• tier4_perception_rviz_plugin
• tier4_planning_rviz_plugin
• tier4_state_rviz_plugin
• tier4_system_rviz_plugin
• tier4_traffic_light_rviz_plugin
• tier4_vehicle_rviz_plugin
• time_utils
  • refactor(time_utils): prefix package and namespace with autoware autoware.universe#9173
• traffic_light_recognition_marker_publisher
• traffic_light_utils
  • refactor(traffic_light_utils): prefix package and namespace with autoware autoware.universe#9251
• tvm_utility
  • refactor(tvm_utility) prefix package and namespace with autoware autoware.universe#9241

[esteve]

@youtalk would it be useful to list the packages in common here so that we can check if they are truly "common" or can be moved?

[youtalk]

@esteve It's good idea! Please do it.

[esteve]

@youtalk I've updated the issue description with a list of packages from common

[esteve]

I think the rviz plugin packages can most likely be moved elsewhere, this would make the OpenAD Kit Docker base images smaller.

[youtalk]

Yeah, that's why #5076 was created.

[esteve]

@youtalk some of the packages in common are rviz plugins, I think it'd be best to move the plugins elsewhere so we can make a smaller base image for OpenAD Kit, I'm focusing on refactoring the packages (adding the autoware prefix) that are not rviz plugins

[esteve]

@youtalk should the packages that have a tier4 prefix also have an autoware prefix? Or should they be renamed to only have autoware as their prefix?

[youtalk]

@esteve Thank you for your feedback.

@youtalk some of the packages in common are rviz plugins, I think it'd be best to move the plugins elsewhere so we can make a smaller base image for OpenAD Kit, I'm focusing on refactoring the packages (adding the autoware prefix) that are not rviz plugins

Exactly. I think it would be a good idea to move all the RViz plugin packages either directly under autoware.universe or under the tools directory.
@mitsudome-r @xmfcx What do you think?

@youtalk should the packages that have a tier4 prefix also have an autoware prefix? Or should they be renamed to only have autoware as their prefix?

For now, let’s keep the package names with the tier4 suffix unchanged.

[xmfcx]

I agree with moving them to reduce the base image size 👍

Some of the rviz plugins are crucial for running the Tutorials. (Basically any rviz plugin included in the main rviz config)

To alleviate this, we can first update the docs and then move.

Actions:

1. Update https://autowarefoundation.github.io/autoware-documentation/main/installation/autoware/source-installation/#how-to-set-up-a-workspace and https://autowarefoundation.github.io/autoware-documentation/main/installation/autoware/source-installation/#how-to-update-a-workspace to include vcs import src < tools.repos
2. Move the packages to tools