TCP multiple descriptors

[jparisu]

Add Regression Test of TCP communication with multiple TCP descriptors.

Description

This test should work as the TCP one and expected not to fail, but the communication is never established and so it fails with timeout.

NOTE: there is a commit adding logs to facilitate the debugging of the test.

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.
• Any new/modified methods have been properly documented using Doxygen.
• Fast DDS test suite has been run locally.
• Changes are ABI compatible.
• Changes are API compatible.
• Documentation builds and tests pass locally.
• New feature has been added to the versions.md file (if applicable).
• New feature has been documented/Current behavior is correctly described in the documentation.

Reviewer Checklist

• Check contributor checklist is correct.
• Check CI results: changes do not issue any warning.
• Check CI results: failing tests are unrelated with the changes.

[JLBuenoLopez]

@jparisu What is the status of this draft? Can it be closed? Is there work planned to move it forward?

[jparisu]

This was a test/demonstrator to check if Fast DDS supportsmultiple TCP transport descriptors in the same Domain Participant.
The result of the test was that it does not, but it is probably a required feature for future tools.
@rsanchez15 what should we do about this?