decide how to account for changes in taxonomy output format

Quoting Ate from HIPPLUG-1269:

Because we now use a new model where the translation "message" property now (properly) is renamed to "name", the Content REST HippoTaxonomyVisitor class now produces backwards incompatible output ("message" -> "name"). So we are looking at either an additional 'upgrade instruction for Content REST api users, or need to think about versioning (and then providing a backwards compatible visitor implementation as well)...