feat(docker): rename multi-stages

[youtalk]

Description

As mentioned in this opinion #5164 (review) by @oguzkaganozt, the Dockerfile is becoming increasingly complex for the following reasons:

• It's unclear from the stage names which stage is the development container and which stage is the runtime container.
• Since the image name is "autoware," adding "autoware" to the stage names (tag names) is redundant.

Therefore, this PR introduces the following naming conventions to make it easier to maintain a one-to-one correspondence between development and runtime containers, even as multi-container setups become more prevalent:

• Containers with the suffix -devel are development containers, while those without the suffix are runtime containers.
• The prefix autoware- is no longer used.

The generated images will have names like the following.

Before	After
autoware:latest-base	autoware:latest-base
autoware:latest-autoware-core	autoware:latest-core-devel
autoware:latest-autoware-universe	autoware:latest-universe-devel
autoware:latest-devel	autoware:latest-devel
autoware:latest-runtime	autoware:latest-universe

Before:

After:

Tests performed

youtalk#102
https://github.com/youtalk/autoware/actions/runs/10712585980

Effects on system behavior

Documentation, shell scripts, and the GitHub Actions settings in the autoware.universe repository also need to be updated.

Interface changes

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[xmfcx]

@youtalk -san, could you also update the https://github.com/autowarefoundation/autoware/tree/main/docker#readme too when making these changes?

Referred in issue:

• Update the docker images readme file to match the new updates #5176

[xmfcx]

@youtalk -san, I think the latest keyword is also becoming redundant, what do you think of removing it?
Is there a benefit in keeping the latest keyword?

Before	After
autoware:latest-base	autoware:base
autoware:latest-core-devel	autoware:core-devel
autoware:latest-universe-devel	autoware:universe-devel
autoware:latest-devel	autoware:devel
autoware:latest-universe	autoware:universe

Referred in issue:

• Remove the latest keyword from docker tags #5175

[kaspermeck-arm]

@youtalk -san, I think the latest keyword is also becoming redundant, what do you think of removing it? Is there a benefit in keeping the latest keyword?

Before After
autoware:latest-base autoware:base
autoware:latest-core-devel autoware:core-devel
autoware:latest-universe-devel autoware:universe-devel
autoware:latest-devel autoware:devel
autoware:latest-universe autoware:universe
Referred in issue:

• Remove the latest keyword from docker tags #5175

If we remove the latest tag, how would we deal with timestamped tagging, e.g., autoware:devel-2024Q4?

[xmfcx]

If it has timestamp, it can have the timestamp in the tag. If it doesn't have a timestamp (it is latest) it will be without latest keyword.

[oguzkaganozt]

Whenever user pulls an image, say autoware:universe it would always pull the relevant latest image anyways because we are overwriting it with the newest one on each push. In that manner we do not need to have latest tag really.

On the other hand latest tag should be unique and only be used for the one image not for all other alternative image types.
And for our case it would be the universe(monolithic runtime image) for the autoware, so like autoware:latest would be equal to latest autoware:universe always.

[oguzkaganozt]

@youtalk I think we should remove the latest tag as we finalized monolithic images, we are already overwriting core and universe images with the same name anyways.

@xmfcx thanks for the heads up !