Uses ros-action-ci in build.yaml workflow.

[francocipollone]

Part of maliput/maliput_infrastructure#274
Related to maliput/maliput_infrastructure#268

Signed-off-by: Franco Cipollone franco.c@ekumenlabs.com

[francocipollone]

CI is failing when running some tests because before running the tests we were requiring to source the install folder, in order to let envars like MALIPUT_MALIDRIVE_RESOURCE_ROOT (which points to install/maliput_malidrive/share/resources) to be valid(via environment hooks).

Some test looks for the resources via this environment variable.
An example of this can be found at

maliput_malidrive/test/regression/base/road_geometry_test.cc

Line 81 in 7136af9

xodr::LoadDataBaseFromFile(utility::FindResource("odr/SingleLane.xodr"), kParserConfiguration);

I assume this is something that will also be a blocker when pushing maliput_malidrive into the ros build farm.
Given that it seems that this needs a refactor, what would be the best approach to follow having in mind other ROS2 packages that may find the same issue?. @agalbachicar @tfoote .

It comes to my mind to add a compile definition pointing to the install/src folder but maybe there is a more ros2-way of doing this.

[francocipollone]

I merged #219 into this branch. Retriggering CI

[francocipollone]

Going in as it was approved at #219