Fixes a bug where `('company_id', '=', company_id)` would pretty much immediately get replaced by the domains from the onchange, so was essentially useless.

The conditional could be replicated in two ways: one would be to use a python-level conditional expression:

    a if cond else b

this is easier for users to interpret, but harder to analyze: python expressions are currently opaque to view analysis (and probably the eventual domain edition).

The alternative here is to leverage domain simplification:

    (OR (= (not cond) 1) section)

if `cond` is true becomes

    (OR (= 0 1) section)

and thus `section` itself, while if `cond` is false it becomes

    (OR (= 1 1) section)

and thus `true` (so the section doesn't apply).

It works OK though the inversion of the condition itself is a bit bizarre.

And in this specific case since we need both branches the negated condition requires explicitly converting the condition to a boolean if it might not be one: the expression compiler recognizes specifically `(= 0 1)` and `(= 1 1)` (`(= False 1)` and `(= True 1)` also work for Python reasons).

Task 2115472

Also the fix on analytic_account_id is the sort of reasons why we'd want the ability to *edit* domans rather than just replace them.