[21055] Automatically unmatch remote participants on participant deletion

[MiguelCompany]

Description

It's been reported that when several participants are created in the same process, and log warnings are enabled, a call to delete_participant() triggers the following warning several times:

[RTPS_READER Warning] Automatically unmatching on ~WriterProxy -> Function ~WriterProxy

Debugging revealed that these were shown for the built-in reliable readers.

This PR adds a mechanism to automatically unmatch the built-in endpoints when a participant is deleted.
The mechanism consists of performing the same actions executed when receiving a DATA(p|UD), without triggering the participant listener.

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.
• N/A New feature has been added to the versions.md file (if applicable).
• N/A New feature has been documented/Current behavior is correctly described in the documentation.
• [NO] Applicable backports have been included in the description.
  • Backport to 2.14.x will be done manually, and we will backport to the supported branches from that one

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.

[MiguelCompany]

@richiprosima Please test_3 this

[elianalf]

@richiprosima please test_3 this