Fix LoadFromBag assumptions causing C++ exceptions during serialization (backport #438)

[mergify]

Description

• Not all bags have only GridMap messages
• Not all bags have GridMap on the right topic
• Add test for trying to load a grid map from a bag that doesn't contain it on the expected topic
• Add nullptr check on reader messages

Demo

Details

I uploaded a super small bagfile of two chatter topics. It's very small:

ryan@B650-970:~/Dev/ros2_ws/src/grid_map/grid_map_ros$ ll -h resource/double_chatter/
total 56K
drwxrwxr-x 2 ryan ryan 4.0K Feb 16 11:48 ./
drwxrwxr-x 3 ryan ryan 4.0K Feb 16 11:49 ../
-rw-r--r-- 1 ryan ryan  40K Feb 16 00:50 double_chatter.db3
-rw-rw-r-- 1 ryan ryan 4.8K Feb 16 11:48 metadata.yaml

It might be better to construct the bag file on the fly in the test case, but that would take much more time than what I did here.

Issue

Solves #401

---

This is an automatic backport of pull request #438 done by Mergify.

[Ryanf55]

@wep21 Looks like nav2 broke ABI again with their rosdep sources. Thoughts on only compile nav2 from source on rolling?

[wep21]

@Ryanf55 How about adding if condition into vcs import block?

[Ryanf55]

@Ryanf55 How about adding if condition into vcs import block?

To make it only import them if $ROS_DISTRO==rolling?

[Ryanf55]

Interestingly, the humble branch doesn't contain that vcs import task. The failures here are from uncrustify, perhaps caused by a version difference between the binary in ubuntu 24 and the one in ubuntu 22. If the corresponding Iron PR fails CI too after I force-pushed it, I think it's pretty clear the code formatter changed and is going to mean backporting stuff regularly from Ubuntu 24 to Ubuntu 22 could be hard.