[22519] Decouple transport receivers creation using unique network flows

[juanlofer-eprosima]

Description

This is a follow-up of #5461, attempting to solve ros2/ros2#1617.

In that concrete scenario (where builtin + TCP transports are used in clients), the problem is that while the TCP (and UDP) transports are rightly able to create a receiver in the dedicated "unique flow" port, shared memory fails for that same port as the other process is already listening on it. However this was not being handled properly, so once matched, the publisher attempts to send data to the wrongfully announced shared memory locator.

Note that the underlying problem is that, when creating unique network flows, all transports are requested to create a receiver for a specific port all together. This is, the creation of unique flow receivers is only considered to fail when it fails for all transports, instead of decoupling them and keep trying for alternative ports when the creation of a specific transport receiver fails. The present PR fixes this behavior.

@Mergifyio backport 3.1.x 3.0.x 2.14.x 2.10.x

Contributor Checklist

• Commit messages follow the project guidelines.
• The code follows the style guidelines of this project.
• Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• N/A Any new/modified methods have been properly documented using Doxygen.
• N/A Any new configuration API has an equivalent XML API (with the corresponding XSD extension)
• Changes are backport compatible: they do NOT break ABI nor change library core behavior.
• Changes are API compatible.
• N/A New feature has been added to the versions.md file (if applicable).
• N/A New feature has been documented/Current behavior is correctly described in the documentation.
• Applicable backports have been included in the description.

Reviewer Checklist

• The PR has a milestone assigned.
• The title and description correctly express the PR's purpose.
• Check contributor checklist is correct.
• N/A If this is a critical bug fix, backports to the critical-only supported branches have been requested.
• Check CI results: changes do not issue any warning.
• Check CI results: failing tests are unrelated with the changes.

[cferreiragonz]

Tested that the PR solves issue ros2/ros2#1617 with Fast DDS 3.x and in Rolling with Fast DDS 2.14.x

[cferreiragonz]

Just a small NIT.

[MiguelCompany]

LGTM

[cferreiragonz]

LGTM too

[cferreiragonz]

@Mergifyio backport 3.1.x 3.0.x 2.14.x 2.10.x

[mergify]

backport 3.1.x 3.0.x 2.14.x 2.10.x

✅ Backports have been created

• #5588 [22519] Decouple transport receivers creation using unique network flows (backport #5583) has been created for branch 3.1.x
• #5589 [22519] Decouple transport receivers creation using unique network flows (backport #5583) has been created for branch 3.0.x
• #5590 [22519] Decouple transport receivers creation using unique network flows (backport #5583) has been created for branch 2.14.x but encountered conflicts
• #5591 [22519] Decouple transport receivers creation using unique network flows (backport #5583) has been created for branch 2.10.x but encountered conflicts