Separation of autoware_common to autoware_cmake, autoware_utils and autoware_lanelet2_extension

[youtalk]

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

This issue manages the task of splitting and migrating from autoware_common to autoware_cmake, autoware_utils, and autoware_lanelet2_extension.

Purpose

https://github.com/orgs/autowarefoundation/discussions/4671

Possible approaches

• feat(autoware.repos): import autoware_lanelet2_extension #4912
• feat(autoware.repos): import autoware_cmake and autoware_utils #4914
• feat(autoware.repos): use autoware_cmake, autoware_utils and autoware_lanelet2_extension instead of autoware_common #4909
• feat: add autoware_ prefix to lanelet2_extension autoware.universe#7640
• feat: add autoware_ prefix to lanelet2_extension tier4/scenario_simulator_v2#1300
• Archive https://github.com/autowarefoundation/autoware_common

Definition of done

The above tasks will be checked

[xmfcx]

https://github.com/autowarefoundation/autoware_common is archived.

But it contains lanelet2_extension and lanelet2_extension_python packages and still is referenced by autoware.repos file.

And we have https://github.com/autowarefoundation/autoware_lanelet2_extension which has autoware_lanelet2_extension and autoware_lanelet2_extension_python packages.

What steps should be done to remove autoware_common from the autoware.repos file?

[youtalk]

@xmfcx Some of the downstream repositories still need to use the old autoware_common.
tier4/scenario_simulator_v2#1300 (comment)
That's why I cannot remove the autoware_common from autoware.repos for now.