VTOL architecture working with caipirinha

Is there ever a situation where rate set point and virtual rate set point are both published? If not, please only keep the rate set point, and initialise things better like this:

```
class {
...
orb_id_t _rate_id;
...
}

constructor:
if (vtol) {
_rate_id = ORB_ID(virtual rates);
} else {
_rate_id = ORB_ID(rates);
}

publication function:
orb_publish(_rate_id, _rate_sp_pub, &_rates_sp);
```

Doing it this way will make up much cleaner code and make the virtual topics non-intrusive.