Improve consistency of effect "beta" columns and "OR" columns

[mikegloudemans]

Add an assertion to munge script to make sure OR doesn't have negative value (if it does, it should simply be specified as an effect size instead)

In fact for simplicity...maybe ALL OR traits should actually be expressed in log form, to avoid annoyance downstream? We could just say in the coloc pipeline that we're going to use a beta? Could still include both, but beta should represent logOR, then could remove OR altogether from coloc script to avoid confusion, and tell people how to transform OR to beta...

But also, how does SE work when an OR is specified? I assume that's relative to the OR and not the log OR? Probably need to figure that out. Could probably still normalize OR somehow