chore(docker): add -DFORCE_CUDA=1 option to strictly build CUDA related packages

[youtalk]

Description

• fix(docker): install CUDA developement libraries into -devel-cuda images #5446

Following #5446 (review), this PR adds the -DFORCE_CUDA=1 option when performing the colcon build for universe-sensing-perception-devel-cuda, ensuring that the build is not skipped and always executed. This guarantees that the -devel-cuda image has the CUDA development libraries installed.

Tests performed

Not applicable.

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.

[amadeuszsz]

LGTM

[amadeuszsz]

@youtalk
Thanks for this PR! DId you start refactor universe packages? If so, please close this PR in favor of your changes.
Otherwise let's merge this PR and then we can check if CI fails in linked PR.

[youtalk]

I mistakenly thought the FORCE_CUDA option was already supported by default. When I tested it on a local container, the option was ignored. I will try a different method to enforce the build of CUDA packages.