fix broken calls to EVAL in ml_translatorLib.finalise_module_translation

Another case of the_compset containing too much or the wrong stuff,
partly to do with problems with MEM and partly to do with prim_sem_env
(which should not be evaluated according to its definition).

I added two different compsets here, because if I try to combine
everything in one, then one of the usages blows up. Not exactly sure
why.
change the update_precondition from repl_step to basis_repl_step

this doesn't seem to do anything either way, though. what is the point
of this call to update_precondition?
updates to the bootstrap

mainly for the reorganised compsets

also replace compile_primitives with prim_env