Fix ABI compliance

[richiware]

Description

Fix ABI compliance

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

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for c602b46.

❌ Job Failures

Pipeline	Job	Health on master	Retries	🔍 CI Insights	📄 Logs
Fast DDS MacOS CI	mac-ci / fastdds_test ()		0	View	View
Fast DDS Ubuntu CI	ubuntu-ci / fastdds_test (RelWithDebInfo)		0	View	View
Fast DDS Windows CI	windows-ci / fastdds_test (RelWithDebInfo, examples), v142		0	View	View
	windows-ci / fastdds_test (RelWithDebInfo, examples), v143		0	View	View

[emiliocuestaf]

LGTM with green CI