[21293] Fix destruction data-race on participant removal in intra-process (backport #5034)

[mergify]

Description

This PR addresses a race issue happening in stressed intraprocess scenarios when EDP's writer intends to use the remote local reader pointer of an already removed participant. This happens because the participant hasn't received the other's one disposal yet (as it goes through transport).

Some ci flaky tests have already been identified to be related with this issue.

The proposed solution introduces a new state in the Readers LocalReaderViewStatus in which the reader will notify that it is inactive as soon as it is destroyed and noone is using it.
On the other side, the remote local writers using pointers to it, now holds a LocalReaderPointer which wraps the raw reader's pointer plus the view. An internal counter now accounts for the number of references.

Thanks @MiguelCompany for helping with the final's solution design.

Note: the test may be launched with --restest-until-fail 20 or so, in order to reproduce the issue. For a more frequent failure, review can launch the colcon test with the taskset -c 0,1 prefix to make the test to stress more and make it fail more frequently.

@Mergifyio backport 3.1.x 3.0.x 2.14.x 2.10.x

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.

• 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.

---

This is an automatic backport of pull request #5034 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 456e45f has failed:

On branch mergify/bp/2.14.x/pr-5034
Your branch is up to date with 'origin/2.14.x'.

You are currently cherry-picking commit 456e45f25.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   src/cpp/rtps/reader/LocalReaderPointer.hpp
	new file:   src/cpp/utils/RefCountedPointer.hpp
	new file:   test/unittest/utils/RefCountedPointerTests.cpp

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   include/fastdds/rtps/writer/ReaderLocator.h
	both modified:   include/fastdds/rtps/writer/ReaderProxy.h
	both modified:   src/cpp/rtps/RTPSDomain.cpp
	both modified:   src/cpp/rtps/RTPSDomainImpl.hpp
	both modified:   src/cpp/rtps/participant/RTPSParticipantImpl.cpp
	both modified:   src/cpp/rtps/participant/RTPSParticipantImpl.h
	deleted by us:   src/cpp/rtps/reader/BaseReader.cpp
	deleted by us:   src/cpp/rtps/reader/BaseReader.hpp
	both modified:   src/cpp/rtps/writer/ReaderLocator.cpp
	both modified:   src/cpp/rtps/writer/StatefulWriter.cpp
	both modified:   src/cpp/rtps/writer/StatelessWriter.cpp
	both modified:   test/blackbox/common/DDSBlackboxTestsBasic.cpp
	both modified:   test/mock/rtps/ReaderLocator/fastdds/rtps/writer/ReaderLocator.h
	both modified:   test/unittest/utils/CMakeLists.txt

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[MiguelCompany]

Just one stupid NIT

[Mario-DL]

This is RTM, failed tests are unrelated with the changes. Same failures as in nighties