fix unit tests from commit 797a171's float32 precision issues.

[Rosayxy]

---

Basic Info

Info	Please fill out this column
Ticket(s) this addresses	(add tickets here #1)
Primary OS tested on	Ubuntu
Robotic platform tested on	Unit tests
Does this PR contain AI generated software?	No
Was this PR description generated by AI software?	No

---

Description of contribution in a few bullet points

The unit tests added in commit 797a171 has floating point precision issues (caused by converting 1e-6 to float32). Fixed this problem by using std::nextafterf(1e-6f, std::numeric_limits<float>::infinity()); for comparison.

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-*.

[mini-1235]

Please fix linting :)

[Rosayxy]

Linting fixed!