Followup to #4017 addressing a potential issue I noticed whilst
refactoring the SMT interface in booster. Namely, we set the hard-coded
timeout value when checking the consistency of the prelude, before
setting the user supplied value for general queries. This PR instead
just sets the user supplied timeout value before checking the prelude.