feat(colcon-build): source /opt/autoware/setup.sh if exists

[youtalk]

Description

In the current autoware images, the build artifacts of Autoware are saved under /opt/autoware.

https://github.com/autowarefoundation/autoware/blob/main/docker/Dockerfile#L158
https://github.com/autowarefoundation/autoware/blob/main/docker/scripts/build_and_clean.sh#L15

Therefore, in order to reference these artifacts, it is necessary to source /opt/autoware/setup.sh.
This PR makes that change. By doing so, it is expected to reduce unnecessary repository references in build_depends.repos and shorten the build time.

Tests performed

• chore: test updated colcon-build action youtalk/autoware.core#2
• feat(colcon-build): source /opt/autoware/setup.bash if exists youtalk/autoware-github-actions#2
• https://github.com/youtalk/autoware.core/actions/runs/13694329844/job/38293387944?pr=2

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.

[xmfcx]

@youtalk -san, what do you think of removing the /opt/autoware completely from the development images?

It's understandable to have them for the runtime images.
But for the dev&ci images, the established way of working with the Autoware is to mount it and keep building from there. This makes sure the build/install folders stay persistent.

At least, for the CI we don't use this folder at all and it introduces about 700MB additional space.

[youtalk]

I was not aware until now that the /opt/autoware was not being used at all in the CI for autoware.core/universe. That’s why I created this PR.

Also, if we decide to keep the build directory, the size of the development container will increase, leading to more disk space issues. The size of the install directory remains the same whether it is stored locally or in /opt/autoware.

[xmfcx]

I see, I would suggest removing autoware's build and install folders from the container image since they occupy a lot of space.

[youtalk]

@xmfcx Not only comment but also review this please 🙏

[xmfcx]

In order to reduce the container image sizes, I'm opposed to relying on /opt/autoware in the CI.

And will work towards removing that folder to reduce the image size.

This folder is not used in the CI so far. And as I've stated in the PR that would make use of this:

• feat: no longer use build_depends.repos autoware.core#239 (comment)

There are better ways to overcome that issue.

[youtalk]

I started installing to /opt/autoware in August last year, so if you didn’t mention it back then, it’s too late now.
autowarefoundation/autoware#5117
Reverting to the prebuilt/dev stages from 1 year ago would be quite hard...