Reconfigured run_benchmarks CI so that it can be conducted all moveit_benchmarks reliably

[CihatAltiparmak]

With this PR, it's aimed to conduct benchmark in github action and then to visualize all the benchmark results as well.

1. Using this repo's own docker image, we just run run_benchmarks.sh for each middleware. But all benchmarks run inside one job because it's not guarantied that github uses same machine in every job. This blocks the reliability of benchmarks which runs on github action's runners. For example:

In above picture, you can see the plots related to the results of scenario basic service client. Until 133944c commit, you can see the unreliable results. After 133944c commit, graph starts to show the real plots. we still cannot guarantee comparison between commits, but seems we can at least guarantee the comparison in same commit between middlewares.

[henningkayser]

This looks good to me, overall. I would only suggest combining the runs into a matrix by using value substitution for cyclonedds and fastrtps, similar how the MoveIt job runs the same thing for different distros https://github.com/moveit/moveit2/blob/main/.github/workflows/ci.yaml#L18