[21672] Fix data race in TypeObjectFactory::get_instance (backport #5238)

[mergify]

Description

While debugging an error reported by LeakSanitizer in #4916, an important data race was discovered in TypeObjectFactory::get_instance.

The test that PR adds is creating several writers from different threads simultaneously.

This leads to calling TypeObjectFactory::get_instance when registering the local writer (during the creation of its WriterProxyData).

The data race made several factories to be constructed, but only one was assigned to the global g_instance pointer.

Only one of the factories was destroyed when the process finished, making LeakSanitizer complain.

This PR adds a mechanism based on an atomic enumeration holding the state of the singleton instance.

@Mergifyio backport 2.14.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

• N/A: 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.

• [x]: Applicable backports have been included in the description.

  • This was discovered in 2.10.x, so this PR targets that branch.
  • It is also present in 2.14.x, so this PR can be directly forward ported to that branch. Marked so above.
  • For 3.x, the interfaces have changed, and the implementation is based on a static shared_ptr, to it is enough to add a test similar to the one in this PR.

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 #5238 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 8f4b4a5 has failed:

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

You are currently cherry-picking commit 8f4b4a583.
  (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:
	modified:   include/fastrtps/types/BuiltinAnnotationsTypeObject.h
	modified:   include/fastrtps/types/TypeObjectFactory.h
	modified:   src/cpp/dynamic-types/BuiltinAnnotationsTypeObject.cpp
	modified:   test/unittest/xtypes/XTypesTests.cpp

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   src/cpp/dynamic-types/TypeObjectFactory.cpp

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