Implement the abichecker run on devel builds

[j-rivero]

The PR tries to implement the ABI checking for ROS2 packages (issue #678).

The approach followed was to use implement the option of abi checking in the build_and_install.py script used by the devel scripts. I've implement an argument in the script named --abi-checker that runs the auto-abi-checker tool using:

1. The workspace installation space
2. The debian packages associated to the ROS repository under testing.

Testing:

• Using the build_and_install.py script directly on my local system the runs of simple packages (rclcpp) was succesful.
• I'm not sure about the best wait to test this in the ROS2 build farm. Last time I used a testing instance of a buildfarm (I think @nuclearsandwich is generating one these days). If there is a faster approach, please let me know.

Open questions and TODO:

• Still need to resolve the question in Implementation of abichecker for ROS2 #678 about how are we going to identify which packages needs ABI. The easiest thing would be the abi-checker always. If the package does not provide any .h or .so the checker will probably do nothing and report success.
• Export results in Jenkins (the osrf buildfarm uses HTML publisher + Console parser to make build unstable.)
• The local test build fails miserably on packages that has msgs generation support due to the lack of headers related to context and opensplice (not sure if the buildfarm is installing all the support for them). Support to remove the headers of these DDS implementations can be added to the auto-abi-checker.
• There are problems with packages (i.e: gazebo_ros_pkgs) that introduce boost headers into the mix of headers to check (some expected definitions are missing). I'm still investigating them.

[dirk-thomas]

I will leave it up to @nuclearsandwich to recommend how to test deploy this.

[dirk-thomas]

Btw. the current state severely breaks CI which needs to be address before it even makes sense to test deploy this.

[nuclearsandwich]

Aside from one comment which can go either way, I think this is ready. Thanks for iterating @j-rivero.

[j-rivero]

Not sure what happened with Travis but seems like it is not running on my last changes. I can promise that they pass :) .

After/before the merge we need to install the Jenkins plugins:

• HTML publisher
• Console parser

[dirk-thomas]

@j-rivero Please squash merge whenever is ok (not sure of the Jenkins masters need to be updated before, probably not since no repo uses the new flag?).