Stop inserting data into parent tables

[emord]

@dimagi/scale-team This is a change list after merging maxtepkeev#45 into the branch that we run on prod. There is some background in maxtepkeev#26 and maxtepkeev#43 but the gist of it is the way architect works by default is to insert into the parent & child tables, return the id, delete from the parent table.

By default this does nothing differently. If we add the return_null option, this will change it to only inserting into the child table and not returning the ID. this can break in django if we try to use the returned record (i.e. you need to handle the primary key in python code), but I plan to use this for UCRs so we only need to worry about sqlalchemy

[snopoke]

Haven't done a full review, let me know if you need me to.

[emord]

This was pointed to by dimagi/commcare-hq#21994 which is now merged. I also rebuilt the current triggers so that they are inserting directly to the child tables.

We're still using a tag because I don't think either of these two PRs will get merged upstream. I think depending on the citus stuff we may end up removing this dependency anyways, so I'm going to keep this as pointing to a tag. If we still need this afterwards I will come up with a plan to get this properly versioned. Going to put it in the tech debt trello https://trello.com/c/MxJoiRaV/108-path-forward-for-architect