common: suppressing warnings from catkin-pkg when just building

[jbohren]

This depends on ros-infrastructure/catkin_pkg#114

[jbohren]

This is ready now that the latest catkin_pkg has been released.

[wjwwood]

I don't think it is appropriate to suppress the warnings in all the cases, or at least it's not immediately obvious why each of these instances suppresses the warnings.

Can you expand on why you think it's appropriate to suppress the warnings in each of these cases? If you want to disable them globally then I think it should be a command line configuration and it should not suppress the warnings by default.

The warnings are there for a reason and at least in the case of the package naming conventions we want to expose users to the fact their package name doesn't conform as soon as possible because changing the name of a package is harder the longer you wait. If you know what you're doing then you can disable them, but I just don't see the need to suppress them by default.

[jbohren]

I don't think it is appropriate to suppress the warnings in all the cases, or at least it's not immediately obvious why each of these instances suppresses the warnings.

I've added justifications for each place warnings are suppressed.

One of the irritating things was that often the same warning would be printed out multiple times. Obviously this indicates that catkin build is scraping the same workspaces too many times, but regardless it just didn't work well with the way the catkin_tools command line tools work.

I've also added a formatted list of warnings that will get printed at the bottom of catkin list unless you call it with the --quiet option.

[wjwwood]

Ok, lgtm, thanks.