[15341] Protect access to reader listeners

[MiguelCompany]

Description

This should fix dataraces involving access to the listener on RTPSReader and DataReaderImpl.

Contributor Checklist

• Commit messages follow the project guidelines.
• The code follows the style guidelines of this project.
• N/A Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added.
• N/A Any new/modified methods have been properly documented using Doxygen.
• Fast DDS test suite has been run locally.
• Changes are ABI compatible.
• Changes are API compatible.
• N/A Documentation builds and tests pass locally.
• 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.

Reviewer Checklist

• Check contributor checklist is correct.
• Check CI results: changes do not issue any warning.
• Check CI results: failing tests are unrelated with the changes.

[jsan-rt]

This should be protected as well.

[jsan-rt]

Maybe it would be best to keep the final return clause outside the scope of this mutex.

[MiguelCompany]

This should be protected as well.

I have mixed feelings about this.
On one hand, I feel like protecting RTPSReader::getListener() should be done.
On the other hand, it is called all throughout the RTPS layer code, and the TSan job does not seem to be complaining. This means there are other protections in place whenever the method is called.

My fear is that taking the reader mutex may add ABBA deadlocks...

[jsan-rt]

I'm of the same mind regarding GetListener. Let's just keep it as is for now.

[MiguelCompany]

@richiprosima Please test this