Adding clear costmap around pose service option

[SteveMacenski]

Requires documentation ros-navigation/docs.nav2.org#716

Requires testing by @dw25628

Closes #5296

Generated with Claude Code Sonnet 4

[codecov]

Codecov Report

Attention: Patch coverage is 54.83871% with 14 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
nav2_costmap_2d/src/clear_costmap_service.cpp	17.64%	14 Missing ⚠️

Files with missing lines	Coverage Δ
...vior_tree/plugins/action/clear_costmap_service.hpp	100.00% <100.00%> (ø)
...vior_tree/plugins/action/clear_costmap_service.cpp	100.00% <100.00%> (ø)
nav2_costmap_2d/src/clear_costmap_service.cpp	35.82% <17.64%> (-6.18%)	⬇️

... and 4 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[dw25628]

@SteveMacenski I tested this morning and this works as intended. Apologies for not getting my PR up faster, I was trying to build out better test coverage for the clear costmap services. If you can allow me rights to push to this PR I can push up my addition for costmap clearing unit tests in nav2_costmap_2d. I was hoping to get a more full coverage integration test completed but have not gotten that done yet.

I also have migration documentation updates I can add to ros-navigation/docs.nav2.org#716 if I am granted access.

Any possibility we can backport these changes to Jazzy?

Thanks for all you do

[SteveMacenski]

No worries on the delay - I honestly didn't think the AI would get this one (most of my multi-file refactors it really doesn't do well; this was a smaller one that I was pushing the edge to see if it would work as an experiment). I was mostly just toying around with the new tools.

I was trying to build out better test coverage for the clear costmap services. If you can allow me rights to push to this PR I can push up my addition for costmap clearing unit tests in nav2_costmap_2d

Can you open it up instead as a separate PR? Its easier for us to do that than for me to give you access to the core repo or try to figure out permissions for just this branch. Ditto with the migration guide doc!

If it fixes the issue, I can merge and wait on your PR for more tests 😄

Any possibility we can backport these changes to Jazzy?

I can try an autobackport on merge. If it doesn't work, it would need to be manually cherry picked and have the conflicts resolved

[SteveMacenski]

@dw25628 this isn't able to be autobackported. Please open a cherry-picked PR for Jazzy :-)