Fix buildfarm build of rmf_traffic_editor packages

[luca-della-vedova]

Bug fix

Fix uncrustify test on buildfarm.

Fixed bug

Trying to address buildfarm failure.

My hypothesis is that rmf_utils was not specified as a test dependency, hence the config file would not be found and when running uncrustify it would actually not pass our custom config file (when looking for ament_uncrustify in the log, there is no -c [path to file] argument). Hence my proposed fix is to just add it as a test dependency.
The other line is just a cleanup in the CMakeLists since it still refers to a path in galactic

[luca-della-vedova]

Upon further investigation, it seems this would make the build from UNSTABLE to green, but the real problematic package is rmf_traffic_editor_assets:

Starting >>> rmf_traffic_editor_assets

----------------------------------------------------------------------
Ran 0 tests in 0.000s

NO TESTS RAN
--- stderr: rmf_traffic_editor_assets

----------------------------------------------------------------------
Ran 0 tests in 0.000s

NO TESTS RAN
---
Failed   <<< rmf_traffic_editor_assets [0.00s, exited with code 5]

Seems to be due to a change in upstream Python that changed the return code for NO TESTS RAN from 0 to an error code to detect cases where tests were supposed to be ran python/cpython#98904

[luca-della-vedova]

df611c4 changed the rmf_traffic_editor_assets from a Python to a CMake package, I added the package to the CI and it was red before this commit green with it so it can also act as a regression test for (unlikely) future regressions