[23006] Reduce trace category when failing to unregister type

[juanlofer-eprosima]

Description

PR #5687 added a log error trace to DomainParticipantImpl::unregister_type when attempting to unregister a type that is still being used. As a consequence, several log traces started to appear when deleting ROS 2 nodes, since unregister_type gets called by rmw_fastrtps_shared_cpp::remove_topic_and_type when destroying publications and subscriptions, regardless of whether the type is still being used by other publications/subscriptions. This can make tests checking for error traces to fail, which can be avoided by just reducing the log category.

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

[MiguelCompany]

LGTM with the following green:

• Linux