[20869] Create DomainParticipantExtendedQos class

[LuciaEchevarria99]

Create DomainParticipantExtendedQos class

This PR creates the DomainParticipantExtendedQos class, which extends the functionality of the existing DomainParticipantQos class by adding the domainId member. It also updates the DomainParticipantFactory to support the creation of participants using DomainParticipantExtendedQos.

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 ABI compatible.
• 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: eProsima/Fast-DDS-docs# [20869] Add documentation for DomainParticipantExtendedQos Fast-DDS-docs#805
• 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.
• Check CI results: changes do not issue any warning.
• Check CI results: failing tests are unrelated with the changes.

[elianalf]

We need to include also a small section in Fast DDS docs in Profile based creation of a DomainParticipant and an example in the Profile based creation of a DomainParticipant

I think that you can complete the Contributor Checklist as follow:

• 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)
• N/A 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.
• N/A Applicable backports have been included in the description.