nav2_rviz_plugins: Remove unused rviz_common_plugins include

[traversaro]

Basic Info

Info	Please fill out this column
Ticket(s) this addresses	No ticket.
Primary OS tested on	Windows
Robotic platform tested on	Not tested on a robot
Does this PR contain AI generated software?	No

Description of contribution in a few bullet points

I was experiencing a strange linking error on Windows:

costmap_cost_tool.obj : error LNK2019: unresolved external symbol "public: static struct QMetaObject const rviz_default_plugins::tools::PointTool::staticMetaObject" (?sta
ticMetaObject@PointTool@tools@rviz_default_plugins@@2UQMetaObject@@B) referenced in function "public: static class QString __cdecl rviz_default_plugins::tools::PointTool:
:tr(char const *,char const *,int)" (?tr@PointTool@tools@rviz_default_plugins@@SA?AVQString@@PEBD0H@Z) [D:\j\bld\rattler-build_ros-jazzy-nav2-rviz-plugins_1737308768\work
\build\nav2_rviz_plugins.vcxproj]
mocs_compilation_Release.obj : error LNK2001: unresolved external symbol "public: static struct QMetaObject const rviz_default_plugins::tools::PointTool::staticMetaObject
" (?staticMetaObject@PointTool@tools@rviz_default_plugins@@2UQMetaObject@@B) [D:\j\bld\rattler-build_ros-jazzy-nav2-rviz-plugins_1737308768\work\build\nav2_rviz_plugins.v
cxproj]
D:\j\bld\rattler-build_ros-jazzy-nav2-rviz-plugins_1737308768\work\build\Release\nav2_rviz_plugins.dll : fatal error LNK1120: 1 unresolved externals [D:\j\bld\rattler-bui
ld_ros-jazzy-nav2-rviz-plugins_1737308768\work\build\nav2_rviz_plugins.vcxproj]

while I could not fully understand what was happening, I noticed that the costmap_cost_tool.hpp file was including an header that was not necessary. By removing the unnedded include, the linking error on Windows disappeared.

Description of documentation updates required from your changes

Description of how this change was tested

---

Future work that may be required in bullet points

For Maintainers:

• Check that any new parameters added are updated in docs.nav2.org
• Check that any significant change is added to the migration guide
• Check that any new features OR changes to existing behaviors are reflected in the tuning guide
• Check that any new functions have Doxygen added
• Check that any new features have test coverage
• Check that any new plugins is added to the plugins page
• If BT Node, Additionally: add to BT's XML index of nodes for groot, BT package's readme table, and BT library lists

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

see 5 files with indirect coverage changes