msg validation check for `/initialpose` in `nav2_amcl`

[GoesM]

---

Basic Info

Info	Please fill out this column
Ticket(s) this addresses	#4294
Primary OS tested on	Ubuntu22.04
Robotic platform tested on	gazebo simulation of Tally
Does this PR contain AI generated software?	No

---

Description of contribution in a few bullet points

• make a validation util for array
• make a validation util for PoseWithCovariance
• make a validation util for PoseWithCovarianceStamped
• add test for new changes

• use the validation check for /initialpose in nav2_amcl

Future work that may be required in bullet points

For Maintainers:

• [ ] Check that any new parameters added are updated in navigation.ros.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

[GoesM]

uh.... the error is odd to me error: ‘PoseWithCovarianceStamped’ in namespace ‘geometry_msgs::msg’ does not name a type

My local test (based on ros2-humble) run successfully however failed during CI.

Is the type name different between main and humble ?

[SteveMacenski]

I think you're just missing #include "geometry_msgs/msg/<messsage>.hpp" for the message

[GoesM]

You're right! ^_^

though I'm still confused why it could be built in humble fork ( within my local environment ), T_T, it seems that it doesn't affect much.

I think you're just missing #include "geometry_msgs/msg/<messsage>.hpp" for the message

After all, everything seems fine after changes following your reminder. ^_^