[21745] Add QoS getters from raw XML

[juanlofer-eprosima]

Description

This PR extends public API with methods meant to fill QoS structures given a raw XML string containing pertinent profile configurations. For each QoS getter from XML there are three method variants:

• get_X_qos_from_xml without profile name : the first encountered profile of the expected kind (participant, publisher, etc.) is parsed.
• get_X_qos_from_xml given profile name : fills the QoS structure with the profile whose name coincides with the one provided.
• get_default_X_qos_from_xml : fills the structure with the default profile of the expected kind (participant, publisher, etc.) found in the XML string.

This API extension provides backwards compatibility after having made XMLParser private (done in Fast-DDS 3 release).

Merge after:

• [21745] Fix flow_controllers comparison in DomainParticipantQos equality operator #5295

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.
• 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.
  • Related documentation PR: [21745] Add QoS getters from raw XML Fast-DDS-docs#928
• 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.
• 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.

[richiware]

Partial review

[richiware]

Partial review. Header files.

[richiware]

Partial review. Implementation.