move translatable models to 1:1 related separate tables

[infohata]

basically admin becomes so much unconfigurable if using HVAD. We either have to reimplement everything on frontend CRM (which can reuse HVAD at some degree), but it would be much simplier to just move all translatable fields to separate 1-1 related tables (meaning unique foreign key relationships). This will not add too much weight on the DB.

Opinions needed, will leave it hang for a day or two, as now can work on #7 without touching these.

[infohata]

The decision is to move translatables to related models, to keep it manageable on admin. If/when HVAD situation will improve, we can always migrate the data to at least extended table state, if not merge the tables back.