[24451] Add Topic-Name Profile Lookup for Endpoint Creation

[ZakariaTalbi]

Included support for topic-name profile lookup by adding create_datawriter_with_profile() as the default path in CommonWriter.cpp, with fallback to create_datawriter() when needed.

Added a new test, writer_topic_profile_lookup(), in ParticipantsCreationgTest.cpp to validate the feature, and registered it in CMakeLists.txt.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 60.00000% with 26 lines in your changes missing coverage. Please review.
✅ Project coverage is 36.52%. Comparing base (2d1ed3f) to head (356e74d).

Files with missing lines	Patch %	Lines
...e_participants/src/cpp/reader/dds/CommonReader.cpp	59.09%	1 Missing and 8 partials ⚠️
...e_participants/src/cpp/writer/dds/CommonWriter.cpp	68.18%	1 Missing and 6 partials ⚠️
...ants/src/cpp/participant/dds/CommonParticipant.cpp	57.14%	0 Missing and 3 partials ⚠️
...ticipants/src/cpp/writer/dds/QoSSpecificWriter.cpp	0.00%	3 Missing ⚠️
...pe_participants/src/cpp/writer/dds/MultiWriter.cpp	50.00%	2 Missing ⚠️
ddspipe_yaml/src/cpp/YamlReader_participants.cpp	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #184      +/-   ##
==========================================
+ Coverage   36.09%   36.52%   +0.43%     
==========================================
  Files         174      158      -16     
  Lines       12329     7548    -4781     
  Branches     5634     2998    -2636     
==========================================
- Hits         4450     2757    -1693     
+ Misses       5023     3326    -1697     
+ Partials     2856     1465    -1391     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[juanlofer-eprosima]

Good job! 🥇 We mostly need to decide if XML > YAML or the other way around, we could even add a configuration option to the YAML so we can keep both possibilities and let the user decide.

It is pending to update the documentation of tools using DDS-Pipe.

[juanlofer-eprosima]

Suggested change

	fastdds::dds::ReturnCode_t ret_xml_qos = dds_subscriber_->get_datareader_qos_from_profile(topic_name, qos);
	if (ret_xml_qos != fastdds::dds::RETCODE_OK)
	if (fastdds::dds::RETCODE_OK != dds_subscriber_->get_datareader_qos_from_profile(topic_name, qos))

[juanlofer-eprosima]

I am now thinking maybe we should already return here if the profile is found. There might be scenarios in which a user wants to force a specific durability/reliability or history QoS, and if we override with the YAML configuration values, we would be forcing the user to configure through both XML and YAML. However, it would be beneficial to automatically add QoS such as expect_inline_qos for keyed topics.

[juanlofer-eprosima]

Same suggestion as in reader.

[juanlofer-eprosima]

Same comment as in the reader, in this case writer_data_lifecycle and deadline might need special treatment. Note that in this case overriding the deadline via YAML is not possible.