Robotics Systems Types

Reviewing …

• Renamed ResourceAllocation -> ResourceAllocationRequest (but see first remaining issue)
• fixed copy/paste documentation strings
• Typo fixes

• The descriptions of the resource_ids and location_ids seem insufficient (see http://docs.cor-lab.de/rst-manual/trunk/html/conventions.html#best-practices-for-documentation-strings for repeated fields). Reading "required/allocated" makes me uncertain whether I misunderstood the whole type. It is probably not an allocation request but rather an exchange about resource allocation, right? If so, the documentation string of the message itself should make this clear.
• If the type actually represents an exchange, how is the outcome communicated? Is the message intended to be contained in a TaskState message? If so, the fact should be documented.
• What is meant by "location" in the context of this type?
• Depends on homeautomation types. Can this be avoided to make the type more generally applicable? Also, homeautomation types will probably not be available in this repository for some time.
• The name "NO" of the lowest priority is not very clear.

Attached one additional change: the protocol buffer code generation assumes that field names are singular, even for repeated fields.

Should this type still be added at some point?

Opening a new issue with a revised type.