Test long Studio voc name on supported databases
Goal is to see if long voc names are actually a problem, because the current validation message can frighten people.
Oracle table names have a maximum of 30 characters, but Studio prefixes the names with `studio_vocabulary_` which is 18 chars so that leaves only 12 available. Beyond that length it should work (I haven't checked what Studio does) but the names will be mangled automatically by Nuxeo (using a technical name based on a hash instead).
- Create two long voc name in Studio with the same first characters and deploy them in every supported DB
- Check how NXP behaves
- If behavior is ok, create ticket to adapt or remove validation message accordingly and assign it to a dev team