[21538] Allow all durability configurations

[Mario-DL]

Description

This PR:

• Allows the creation of a DataWriter/Reader with a PERSISTENT durability, but behaving as TRANSIENT.
• When in TRANSIENT, if no persistence guid is given, it fallbacks to TRANSIENT_LOCAL.
• Refactors BB make_transient() make_persitent() pubsub API to be clearer about the intention of making a transient or persistent endpoint.
• Adds BB tests for the purpose.

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.
• 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: [21538] Allow all durability configurations Fast-DDS-docs#907
• 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.
• 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.

[MiguelCompany]

Apart from my comments below, I think we can consider that we fully support PERSISTENT durability, since I think it is what we currently support.

From the standard:

Data is kept on permanent storage, so that they can outlive a system session.

This means we could remove the warning on check_qos