[19036] Discard local SHM locators that cannot be openned

[EduPonz]

Description

This PR adds a is_locator_reachable API to NetworkFactory so that unreachable locators can be discarded while deserializing the DATA(p), DATA(r), or DATA(w) messages. To do so, the NetworkFactory iterates over the transports looking for one that can reach the given locator. It does so using a new TransportInterface::is_locator_reachable API.

This PR partially solves a long standing communication issue when the participants are run in the same host but under different users. This used to cause the Fast DDS participants to keep SHM locators from the remote participant that could not be opened (due to permissions); and since Fast DDS limits the communication to SHM as soon as the remote participant has a reachable SHM locator, communication was not possible.

After this PR:

• ✅ Communication with between two different users with similar permissions works in both directions
• ✅ On a super-user user, subscribing to a topic from a normal user works.
• ❌ On a normal user, subscribing to a topic from a user with more permissions (such as a super-user) still does not work.

Depends on:

• [19036] Link SHM locator kind with Fast DDS major version #5116

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
• 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.
• N/A: 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.

[Mario-DL]

We internally agreed to address the convenient changes to overcome the last requirement on a follow up

[juanlofer-eprosima]

LGTM