Don't ignore rmw_connextdds by default in linux-aarch64

[fgallegosalido]

Description

Currently, the Connext RMW is ignored by default in linux-aarch64. This pull request changes that so it is now used by default in the CI.

Is this user-facing behavior change?

Now the CI doesn't need to explicitly enable the Connext RMW.

Did you use Generative AI?

No

Additional Information

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[fgallegosalido]

@cottsay can you launch a build with the default CI parameters, to be sure the Connext RMW is not ignored?

[cottsay]

This sort of change has to be deployed to be tested, so I deployed it to the "test" launcher job and triggered it:

[fgallegosalido]

Thank you @cottsay! It seems the Connext RMW is no longer ignored in linux-aarch64. However, we are not using the Connext Debian packages (which are required for linux-aarch64). I can't seem to figure out how to always enable them in linux-aarch64, as I thought the change on https://github.com/ros2/ci/blob/master/create_jenkins_job.py#L144 would suffice. Do you have any idea what I am missing?

[fgallegosalido]

@cottsay another question I wanted to ask is what else do we need to do to have ARM as an officially supported architecture in the REP 2000? I'm not sure if that is still getting updated or if there is any other place where the Connext RMW could be considered to support ARM moving forward.