Role cloning treats taxonomies differently in UI and API
Description of problem:
From Hammer CLI, if you clone a role that has taxonomies, then after cloning the same taxonomies are copied over to the cloned role. When clonning in UI, the taxonomies are not selected by default, so role is clonned without taxonomies. We should unify the behaviour.
1. Create a role with org A and location A
2. Clone above role from hammer CLI without providing any org and location id's
- hammer role clone --id 45 --new-name clied_cloned
3. Clone the same role from UI - just click 'clone' and submit without making any custom changes.
The cloned role using Hammer has taxonomies copied from its parent role while role clonned in UI has no taxonomies.
Cloned role should have same taxonomies regardless of whe way they are clonned.