Remove tinyxml2 vendor on rolling

[mini-1235]

In Nav2, we are building BT.CPP from source temporarily, however, we are failing to build now:

#20 2.012 Get:20 http://archive.ubuntu.com/ubuntu noble-backports/main amd64 Packages [49.0 kB]
#20 2.013 Get:21 http://archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 Packages [671 B]
#20 2.013 Get:22 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 Packages [35.6 kB]
#20 3.087 Fetched 41.5 MB in 3s (14.2 MB/s)
#20 3.087 Reading package lists...
#20 4.120 /usr/bin/rosdep:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
#20 4.120   from pkg_resources import load_entry_point
#20 5.248 ERROR: the following packages/stacks could not have their rosdep keys resolved
#20 5.248 to system dependencies:
#20 5.248 behaviortree_cpp: No definition of [tinyxml2_vendor] for OS version [noble]
#20 ERROR: process "/bin/sh -c . /opt/ros/$ROS_DISTRO/setup.sh &&     apt-get update && rosdep install -q -y       --from-paths src       --skip-keys \"         slam_toolbox         \"       --ignore-src     && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 1
------
 > [builder  6/11] RUN . /opt/ros/rolling/setup.sh &&     apt-get update && rosdep install -q -y       --from-paths src       --skip-keys "         slam_toolbox         "       --ignore-src     && rm -rf /var/lib/apt/lists/*:
2.012 Get:19 http://archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Packages [54.1 kB]
2.012 Get:20 http://archive.ubuntu.com/ubuntu noble-backports/main amd64 Packages [49.0 kB]
2.013 Get:21 http://archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 Packages [671 B]
2.013 Get:22 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 Packages [35.6 kB]

4.120 /usr/bin/rosdep:6: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
4.120   from pkg_resources import load_entry_point
5.248 ERROR: the following packages/stacks could not have their rosdep keys resolved
5.248 to system dependencies:
5.248 behaviortree_cpp: No definition of [tinyxml2_vendor] for OS version [noble]
------

I believe this is because tinyxml2_vendor is deprecated and removed on rolling, so I am removing this in rolling.

ref: https://github.com/open-planning/roboplan/blob/6987faf083d5b097b4251f8f698a1a7832c3ac86/roboplan/package.xml#L15-L16

[mini-1235]

It looks like the issue is also due to rolling moved to Ubuntu Resolute, this causes issue when running rosdep on Noble. But I still think this PR is useful, since tinyxml2_vendor is expected to be removed in the future (if I remember correctly, around the Lyrical release)

CMake Deprecation Warning at /opt/ros/rolling/share/tinyxml2_vendor/cmake/tinyxml2_vendorConfig.cmake:34 (message):
  Package 'tinyxml2_vendor' is deprecated (This package will be removed in
  ROS 2 Lyrical Luth.  Instead, use

        distributed package which provides same functionality.)
Call Stack (most recent call first):

[facontidavide]

rolling CI is still failing

[mini-1235]

  $ sudo apt-get -qq install -y --no-upgrade --no-install-recommends ros-rolling-ros-environment | grep -E 'Setting up' 
  E: Unable to locate package ros-rolling-ros-environment
  'sudo apt-get -qq install -y --no-upgrade --no-install-recommends ros-rolling-ros-environment | grep -E 'Setting up' ' returned with 100
'setup_rosdep' returned with code '100' after 0 min 5 sec

I think there's something wrong with industrial ci and we might need to wait a few more weeks

[mini-1235]

I just noticed that the ROS PMC is considering dropping support for the main repository in favor of the testing repository only for Rolling. The CI was failing earlier because there were no syncs for Rolling on 26.04, switching to the testing repo fixed it. Thoughts on this change? @facontidavide

Related:

• https://discourse.openrobotics.org/t/ros-pmc-minutes-for-june-2-2026/55263
• #ROS PMC (Restricted posting) > Rolling Resolute docker images @ 💬

[mini-1235]

@facontidavide does the changes here make sense to you? If yes, can we merge this and cut a new release, please?