Windows fixes from robostack

[gftabor]

---

Basic Info

Info	Please fill out this column
Ticket(s) this addresses	()
Primary OS tested on	( Windows)
Robotic platform tested on	(gazebo simulation of turtlebot)
Does this PR contain AI generated software?	(No)

---

Description of contribution in a few bullet points

Fixes to numerous windows build errors. Robostack has a patch for every single nav2 package fixing it to build on windows. Those are documented here https://github.com/RoboStack/ros-jazzy/tree/main/patch . Predominately made by @traversaro . Actually, building Nav2 from source on Windows requires 15 separate patches being applied.
Other change was running replace all on uint -> unsigned int.

Description of documentation updates required from your changes

Description of how this change was tested

Builds on windows, Nav2 turtlebot demos run.

---

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
• Should this be backported to current distributions? If so, tag with backport-*.

[mergify]

@gftabor, all pull requests must be targeted towards the main development branch.
Once merged into main, it is possible to backport to @jazzy, but it must be in main
to have these changes reflected into new distributions.

[SteveMacenski]

Generally looks good, but there are a few places that need adjustments to be accepted

[SteveMacenski]

I think remaining are the 2x TODOs, the ODE, Robinhood, and updating the realtime prioritization exception text

[gftabor]

Seems like the TODOs were not the correct solution to the core problem. There were 2 declared but never defined slots in rviz_plugins. Robostack got around it by just defining 2 blank functions. #4974 deleted the declaration which seems like a better solution. It was just never backported to jazzy.

Now it should be linting fixes.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files with missing lines	Coverage Δ
...her/include/nav2_constrained_smoother/smoother.hpp	95.93% <100.00%> (ø)
...v2_constrained_smoother/smoother_cost_function.hpp	100.00% <ø> (ø)
nav2_map_server/src/map_io.cpp	92.51% <ø> (ø)
..._smac_planner/include/nav2_smac_planner/a_star.hpp	50.00% <ø> (ø)
...smac_planner/include/nav2_smac_planner/node_2d.hpp	100.00% <ø> (ø)
nav2_util/include/nav2_util/costmap.hpp	100.00% <ø> (ø)
nav2_util/src/node_utils.cpp	82.14% <ø> (ø)
...v2_waypoint_follower/plugins/photo_at_waypoint.cpp	91.52% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[SteveMacenski]

This is significantly slower than the robin hood hashing that we use in the thirdparty directory. Would a major reduction in performance for windows users really be preferable? I think the print out you showed is mostly warnings which can probably be silenced. We have it in the Nav2 codebase so that can be modified and resolved, no?

[SteveMacenski]

Also make sure to sign off with DCO