Fix optimization of some binary comprehensions

If a variable bound in a generator is used as the size of a segment
in the comprehension body, v3_core uses this variable in the code
generated to compute the initial size given to the `bs_init_writable`
primop before the variable is actually bound, as in:

  << <<0:S>> || S <- Slist >>

Reported-By: Peer Stritzinger
Add a new option +clint0 to the compiler

This option makes the compiler run the Core Erlang linting pass before
any optimization pass, which can crash if the given code has unbound
variables, something that is detected by core_lint.