Initial commit

This includes a fully functional plugin loading system and preliminary functionality for event distribution between loaded plugins. The available plugin_ros already inistalized, and controls the ROS interface for this node.
Plugin infrastructure extended, distribution system extended, more plugins; also, bugfixes
Added more plugin code (distribution working better now)
Added skeleton Gazebo plugin

This plugin also includes the showcase implementation of a plugin that uses ROS functionality parasitically. An other plugin initialized the ROS node and maintains the node handle, and this plugin is able to offer services on ROS without having to take care about the setup, and maintenance of the ROS connection.
Plugin dependency lists and automatic dependency loading complete; also, search paths
Plugins loadable by only their (short) names when they are in the search path

The plugin filename must follow the naming convention for plugins (i.e. `libbs_plugin_<plugin-short-name>.so')
Prepared service infrastructure, and added convenience methods for simplifying code in plugins
Include services in cycle data deployment
Implemented skeleton methods for spreading service events
Plugins can now offer services by name
Service calls between plugins is in place and working nicely

The service calls get deployed, collected, spread, and delivered correctly. The results are collected, and forwarded to the original caller.
Fixed a few memory flaws; also, reintroduced context (plan) nodes and got first version of logging working again
Added _actual_ node logging
Added color to output
Reply to ROS service calls with the current id of a newly generated plan node
Fixed a missing initialization flag
Cleaned up, fixed services, added OWL exporter plugin, built pipeline for it

When the ROS node is ordered to export the plan log into a file, the ROS plugin receives it and posts it to all plugins that understand this event. These plugins then request a service `symbolic-plan-tree' from plugins that support it. These plugins then send back their plan trees. In the end, the exporter plugin ends up in a function call, having the original event data from the outside request to export a file, plus the plan log tree data. ready. Three plugins involved, purely internal communication, very flexible and extensible. Yay!
Check for requested export filetype to actually be OWL in the OWL exporter
Integrated formerly prepared OWL exporter class. Compiles, is included, but must still be wired into PluginOwlExporter
Nicification