Move launch and parameter packages into autoware_launch

[xmfcx]

Checklist

• I've read the contribution guidelines.
• I've searched other issues and no duplicate issues were found.
• I've agreed with the maintainers that I can plan this task.

Description

Parent Discussion: Merge launch/configuration repositories under autoware_launch repository #5839

This issue proposes merging several configuration-related repositories into the autowarefoundation/autoware_launch repository. The goal is to simplify the configuration and integration process of Autoware by consolidating related packages under a single repository while maintaining them as separate ROS 2 packages.

Purpose

The current configuration system in Autoware is fragmented across multiple repositories, making it cumbersome for users to manage, version, and customize for their own vehicle setups. This consolidation aims to:

• Reduce complexity for end users and integrators
• Improve maintainability and traceability of configuration changes
• Set the foundation for future improvements to the launch system

Possible approaches

• Move the following repositories into autowarefoundation/autoware_launch as subdirectories/packages:
  • sample_sensor_kit_launch
  • awsim_labs_sensor_kit_launch
  • awsim_sensor_kit_launch
  • single_lidar_sensor_kit_launch
  • sample_vehicle_launch
  • awsim_labs_vehicle_launch
  • autoware_individual_params
• Preserve each as a separate ROS 2 package within the monorepo
• Update documentation and references accordingly
• Archive the original repositories after migration

Definition of done

• Create subdirectories under autoware_launch for each to-be-merged package
• Move each target repository's content into the respective subdirectory
• Ensure each package builds correctly and independently within the new monorepo
• Update any package or launch file references to reflect the new structure
• Test integration and launch flows to confirm functionality remains intact
• Update documentation to reflect the merged structure
• Archive the original repositories

[xmfcx]

List of actions for the sample_sensor_kit_launch:

• Archive the https://github.com/autowarefoundation/sample_sensor_kit_launch to prevent further modifications
  • Update its readme for archiving: docs(README.md): clarify reason for archiving sample_sensor_kit_launch#123
• Move the package under autoware_launch: feat(sample_sensor_kit_launch): move here autoware_launch#1369
• Bump the version of autoware_launch along with its sub-packages.
• Update the autoware.repos and autoware-nightly.repos quickly
  • There will be a short period of duplicate packages for autoware-nightly until we merge this.
• Update the relevant documentation.

[xmfcx]

We'll wait until the next release of Universe is done. Hopefully this Monday (2025-03-24) it'll be finished.

• chore: bump version 0.43.0 autoware_universe#10318

Until then, I'll wait patiently.

cc. @mitsudome-r @rej55 @shmpwk

[mitsudome-r]

We had a discussion among @xmfcx @rej55 @mitsudome-r.

• We will remove the dependency to individual_params rather than merging it to autoware_launch
• We should make the final release of all the sample sensor/vehicle launch before archiving them.
• We will update the autoware.repos file with the latest version.
• We will wait for a week to merge all the launch files.
  • Release new version of autoware_launch (0.43.1)
  • update autoware.repos and autoware-nightly.repos to remove archived repositories