feat(docker): no longer download artifacts on devel image

[youtalk]

Description

https://github.com/orgs/autowarefoundation/discussions/5007#discussioncomment-10086717

Considering these, I would propose to have an image without artifacts for development and CI purposes.
Version with artifacts can be something that derives from this light image.

Based on this opinion, this PR excludes the artifacts from the devel image. The artifacts still continues to be included in the runtime image.

Tests performed

https://github.com/autowarefoundation/autoware/actions/runs/10052443863

Effects on system behavior

Not applicable.

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.

[mitsudome-r]

I'm okay with removing the artifact from the image, but do you have any idea about how the users run ML based nodes with docker?

1. Users download the artifact every time they start up a new container
2. Users download the artifact on host and mount when they run the container

I prefer option 2, but in that case, I think we should be updating the instructions in Autoware Documentation as well to tell the user to download the artifacts and mount them with run.sh script if they wish to use perception nodes. https://autowarefoundation.github.io/autoware-documentation/main/installation/autoware/docker-installation/#runtime-setup

[youtalk]

@mitsudome-r These reverted PRs need to revert again for the developers.
#4864
autowarefoundation/autoware-documentation#571

Note that the runtime image still includes the artifacts.

[xmfcx]

This PR won't help CI because we are using autoware-universe image in CI, not devel.
And autoware-universe images didn't have the artifacts in the first place.

Also posted here:

• feat(ci): update autoware's image tag autoware.universe#7952 (comment)

[youtalk]

Hmm, you mean we don't need this PR?

[xmfcx]

I think it's ok to keep this PR because developers will probably prefer keeping the artifacts outside the image.

But it won't help CI since we use another image for it.