Path trackin conditon node

[silanus23]

---

Basic Info

Info	Please fill out this column
Ticket(s) this addresses	#5037
Primary OS tested on	Ubuntu
Robotic platform tested on	nav2 bringup
Does this PR contain AI generated software?	util test
Was this PR description generated by AI software?	nope

---

Description of contribution in a few bullet points

Description of documentation updates required from your changes

BT node addition
max_error parameter
If there is a document for it maybe upcoming xml

Description of how this change was tested

I tried to take inspiration from is_battery_low condition node. I created unit tests too.

---

Future work that may be required in bullet points

• There is an upcoming xml I will put this in

<RateController hz="3.0">
          <Fallback name="PathTrackingRecoveryPlanner">
            <IsWithinPathTrackingBounds max_tracking_error="2.0" />
            <Fallback name="TieredReplanning">
              <ComputePathToPose goal="{goal}" path="{path}" planner_id="{selected_planner}" error_code_id="{compute_path_error_code}" error_msg="{compute_path_error_msg}"/>
              <Sequence>
                <ClearEntireCostmap name="ClearGlobalCostmap-Tier2" service_name="global_costmap/clear_entirely_global_costmap"/>
                <RetryUntilSuccessful num_attempts="1">
                  <ComputePathToPose goal="{goal}" path="{path}" planner_id="{selected_planner}" error_code_id="{compute_path_error_code}" error_msg="{compute_path_error_msg}"/>
                </RetryUntilSuccessful>
              </Sequence>
            </Fallback>
          </Fallback>
        </RateController>

place this in navigating path through pose xml.

Note:

I had to take out every file with copy paste to a new branch. Cause I had created this branch as a sub branch of the last messy branch. This was the only clean choice that can save me.
I think this will solve my cycling comments and confused commits problem.

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]

@silanus23, your PR has failed to build. Please check CI outputs and resolve issues.
You may need to rebase or pull in main due to API changes (or your contribution genuinely fails).

[SteveMacenski]

I don't think we can set a default here really. I think this needs to be provided explicitly

[SteveMacenski]

For docs: this needs to be having its configuration guide page + add to Navigation Plugins table + migration guide with the larger feature description

[SteveMacenski]

Remove the forward slash, that messes with namespacing

[SteveMacenski]

I don't think node needs to be stored in the class. Just the logger

[SteveMacenski]

I think this should return FAILURE. It must be set to use meaningfully

[SteveMacenski]

What about left vs right different tolerances?

[SteveMacenski]

Suggested change

	RCLCPP_DEBUG(node_->get_logger(), "Initialized IsWithinPathTrackingBoundsCondition BT node");
	RCLCPP_INFO_ONCE(node_->get_logger(), "Waiting for tracking error");
	RCLCPP_INFO(node_->get_logger(), "Initialized IsWithinPathTrackingBoundsCondition BT node");

[SteveMacenski]

We should also check if we've recieved a path tracking error message yet.